I’m experiencing this issue daily on 1.22.0/OSX. In case it helps, I’ve attached a dump for the most recent occurrence (and have plenty more if needed).
Thanks, Andy On 2/4/16, 10:16 AM, "Dave Page" <dp...@pgadmin.org> wrote: >Thanks Sheldon. It's unclear what is causing the issue, as others have >said that 1.20 didn't have this problem, yet the code in your trace >hasn't been touched in 1.22. > >All; it would be really helpful to get more stack traces so I can see >if this is consistently the same issue! > >Thanks. > >On Wed, Feb 3, 2016 at 8:50 PM, Strauch, Sheldon <sstra...@enova.com> wrote: >> PFA A seg fault dump from pgadmin III 1.22.0 RC 1 debug build. This is a >> dump from precisely such an occurrence as mentioned earlier. I encounter >> this on a routing basis since I often move around between groups and even >> floors an lose wireless connectivity from time to time. This fault occurred >> after losing, then restoring connectivity, then clicking on a schema branch >> within the prior-opened database. >> >> Hope this helps. >> >> On Wed, Feb 3, 2016 at 9:05 AM, Adam Pearson <adam.pear...@4finance.com> >> wrote: >>> >>> I’m also having this problem, it also happens if the connection to the >>> server is lost. When you click ‘ok’ ’pgAdmin crashes. >>> >>> >>> >>> As per Lutischán statement below, this was working fine on pgAdmin 1.20. >>> >>> >>> >>> Interestingly, the application is being used (writing queries and >>> executing them against the server it says its lost connection to) but it >>> appears the that management window timesout its connection to the server, >>> which then crashes the program (query window included). >>> >>> >>> >>> This happens rather frustratingly several times a day. >>> >>> >>> >>> Anyone else seeing this? >>> >>> >>> >>> Thanks, >>> >>> Adam >>> >>> >>> >>> From: pgadmin-support-ow...@postgresql.org >>> [mailto:pgadmin-support-ow...@postgresql.org] On Behalf Of Lutischán Ferenc >>> Sent: 26 January 2016 9:05 AM >>> To: pgadmin-support@postgresql.org >>> Subject: [pgadmin-support] PgAdmin III 1.22 crashes, bug riport >>> >>> >>> >>> Dear Developers, >>> >>> >>> >>> We have found a bug in the latest pgAdmin. >>> >>> >>> >>> Software versions: >>> >>> OS: Win7 and WIN10 >>> >>> pgAdmin III 1.22 installed from your build. >>> >>> PostgresSQL 9.3, (I use PostgreSQL 9.5 on local computer only) >>> >>> >>> >>> How to reproduce the bug: >>> >>> - Connect to a remote database >>> >>> - Unplug the network wire >>> >>> - Right mouse click on server >>> >>> - The popup "An error has occurred: server closed the connection >>> unexpectedly" will be showed >>> >>> - Click "OK" >>> >>> - Windows shows message: "pgAdmin III - PostgreSQL Tools stopped". >>> >>> >>> >>> In the 1.20 it is working perfectly. It is a new bug in 1.22. >>> >>> >>> >>> Regards, >>> >>> Ferenc >> >> >> >> >> -- >> >> Assumptions validated by consistent data from actual experiments enable the >> creation of real value. >> >> Sheldon E. Strauch >> Data Architect, Data Services >> O 312-676-1556 >> M 224-723-3878 >> >> Enova International, Inc. >> This transmission is confidential and may be privileged or proprietary. If >> you are not the intended recipient, you are not authorized to use the >> information in this transmission in any way. Please inform the sender >> immediately if you have received this transmission in error and permanently >> delete and destroy the original and any copies of the information. >> >> >> -- >> Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) >> To make changes to your subscription: >> http://www.postgresql.org/mailpref/pgadmin-support >> > > > >-- >Dave Page >Blog: http://pgsnake.blogspot.com >Twitter: @pgsnake > >EnterpriseDB UK: http://www.enterprisedb.com >The Enterprise PostgreSQL Company >
pgAdmin3_2016-02-12-105329.crash
Description: pgAdmin3_2016-02-12-105329.crash
-- Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-support
