pgadmin3 crashed when deleting 10 or more rows of date in a table

Bug #82880 reported by lancewf
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pgadmin3 (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: pgadmin3

The steps to cause the bug
1
. Expand a table in the left explorer window
1. Right click on the table and select View Data (This table holds about 900 rows)
1. Select about 15 rows from the left numbered column
1. Click the delete (the recycle icon)

Then the whole program disappeared. This was not repeatable. The step where preformed again after the crash and the program did not crash. This crash did not cause any data to be corrupted or deleted, as I can tell. This is not a high priority bug.

Thank you for the great software.

lancewf (lancewf)
description: updated
Áron Sisak (asisak)
Changed in pgadmin3:
assignee: nobody → asisak
status: Unconfirmed → Rejected
importance: Undecided → Medium
status: Rejected → Needs Info
Revision history for this message
Isabelle Gaboury (igaboury) wrote :

The same problem arose when deleting even a single row. In the "Edit Data", selected the rows and clicked on the "recycling bin" icon, causing pgAdmin to crash. Appears to be repeatable. Note that the rows were inserted via OpenOffice and ODBC.
Please see attached file.

Revision history for this message
wolfger (wolfger) wrote :

Cleaning up old untouched "incomplete" bugs today, I found this one that should never have been marked incomplete.
Now I need to ask, is this still an issue?

For future reference, "incomplete" is for:
# If you have to ask the reporter questions, set the bug to Incomplete
# Ask the submitter to provide any necessary information in a comment, and make sure you subscribe yourself to the bug report so you will get any updates to the bug via e-mail.
# In the event that a bug has been in the "Incomplete" state for more than 4 weeks, meaning it has not received a response to a request for more information and there is no way someone can work with the bug, the bug status should be changed to "Invalid"

Revision history for this message
lancewf (lancewf) wrote : Re: [Bug 82880] Re: pgadmin3 crashed when deleting 10 or more rows of date in a table

I have not used the newer versions of the software, so I do not know if this
is an issue any longer. On the version of the software that I was using it
was repeatable.

On Sat, Feb 21, 2009 at 2:29 PM, wolfger <email address hidden> wrote:

> Cleaning up old untouched "incomplete" bugs today, I found this one that
> should never have been marked incomplete.
> Now I need to ask, is this still an issue?
>
> For future reference, "incomplete" is for:
> # If you have to ask the reporter questions, set the bug to Incomplete
> # Ask the submitter to provide any necessary information in a comment, and
> make sure you subscribe yourself to the bug report so you will get any
> updates to the bug via e-mail.
> # In the event that a bug has been in the "Incomplete" state for more than
> 4 weeks, meaning it has not received a response to a request for more
> information and there is no way someone can work with the bug, the bug
> status should be changed to "Invalid"
>
> --
> pgadmin3 crashed when deleting 10 or more rows of date in a table
> https://bugs.launchpad.net/bugs/82880
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Lance Finfrock

Revision history for this message
Jan Nekvasil (jan-nekvasil) wrote :

pgadmin3 1.8.4-3, Jaunty. I just tried to delete 5, 10, 20, 30 rows selected continually, then 10 rows selected randomly from small testing table, all without any problems.

Revision history for this message
Guillaume Lelarge (guillaume-lelarge-info) wrote :

I also tried on a 1.10 release. No problems.

Revision history for this message
Stef Walter (stefw) wrote :

Repeatable for me on karmic.

Often if i select more than one row, pgadmin3 says it's deleting many millions. Once I confirm the deletion, the program crashes.

pgadmin3:
  Installed: 1.10.0-1
  Candidate: 1.10.0-1
  Version table:
 *** 1.10.0-1 0
        500 http://archive.ubuntu.com karmic/universe Packages
        100 /var/lib/dpkg/status

Revision history for this message
nehxby (nehxby-gmail) wrote :

Repeatable for me on 9.10.

Program crashes when i delete rows from table with cascading restrictions

pgadmin3:
  Installed: 1.10.0-1
  Candidate: 1.10.0-1

Revision history for this message
rusivi2 (rusivi2-deactivatedaccount) wrote :

Thank you for reporting this bug.

Does this issue occur on Lucid?

Revision history for this message
Jan Nekvasil (jan-nekvasil) wrote :

pgadmin3 1.10.5-1, Ubuntu 10.10. Maverick. Sometimes crashes, sometimes don't. I don't know how to reproduce this bug yet.

Revision history for this message
wolfger (wolfger) wrote :

Over a year later.... Is this still a bug in 11.10?

Revision history for this message
Guillaume Lelarge (guillaume-lelarge-info) wrote :

> Often if i select more than one row, pgadmin3 says it's deleting many millions.

This one has been fixed.

On the non reproduceable delete bug, I cannot say as it is non reproduceable.

Revision history for this message
Hrvoje Lončar (horvoje) wrote :

Yes, it's still a bug.
It occurs randomly, either deleting just one record or many.
I'm using Windows 7 Home Premium 64 bit and pgAdmin III v1.14.1
Willing to provide any needed info.

Revision history for this message
Hrvoje Lončar (horvoje) wrote :

I found this post, maybe it can help:
http://<email address hidden>/msg19605.html

Revision history for this message
Guillaume Lelarge (guillaume-lelarge-info) wrote :

The URL just above is a message sent to pgadmin-hackers. This message contains a patch that is now commited to the pgAdmin source code. The fix will be available with pgAdmin 1.14.3 when it's released.

Áron Sisak (asisak)
Changed in pgadmin3 (Ubuntu):
assignee: Áron Sisak (asisak) → nobody
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for pgadmin3 (Ubuntu) because there has been no activity for 60 days.]

Changed in pgadmin3 (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.