Re: [pgadmin-support] PgAdmin III 1.22 crashes, bug riport

2016-02-16 Thread Dave Page
Cool - thanks. I'll go commit that patch :-) On Tue, Feb 16, 2016 at 3:11 PM, Crain, Andrew wrote: > Dave, > Yes, I did get reconnects, several times (expected), and not one caused a > crash. Looks like you nailed it. > Thanks! > Andy > > From: Dave Page > Date: Tuesday, February 16, 2016 at 5:

Re: [pgadmin-support] PgAdmin III 1.22 crashes, bug riport

2016-02-16 Thread Crain, Andrew
Dave, Yes, I did get reconnects, several times (expected), and not one caused a crash. Looks like you nailed it. Thanks! Andy From: Dave Page mailto:dp...@pgadmin.org>> Date: Tuesday, February 16, 2016 at 5:54 AM To: "Crain, Andrew" mailto:acr...@cincinna.gannett.com>> Cc: "Strauch, Sheldon" mai

Re: [pgadmin-support] PgAdmin III 1.22 crashes, bug riport

2016-02-16 Thread Dave Page
Hi On Tue, Feb 16, 2016 at 3:36 AM, Strauch, Sheldon wrote: > Hi Dave, > > PFA another dump attached. > > This happened again while resizing an SQL window with a moderate-sized > query and a data grid with one column that is extremely large text. > I've just spent 20 minutes or so playing with

Re: [pgadmin-support] PgAdmin III 1.22 crashes, bug riport

2016-02-16 Thread Dave Page
On Mon, Feb 15, 2016 at 9:53 PM, Crain, Andrew wrote: > Dave, > I’ve been using the test build for several hours, longer than the typical > interval between crashes, and have had no problems, including upon > returning to the UI after a connection has become stale, which is when the > problem typ

Re: [pgadmin-support] PgAdmin III 1.22 crashes, bug riport

2016-02-15 Thread Crain, Andrew
ent 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 thi

Re: [pgadmin-support] PgAdmin III 1.22 crashes, bug riport

2016-02-15 Thread Dave Page
>>> >>> >>> >>> >>> 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 wind

Re: [pgadmin-support] PgAdmin III 1.22 crashes, bug riport

2016-02-12 Thread Dave Page
>> 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). > >>> > >>> > >&

Re: [pgadmin-support] PgAdmin III 1.22 crashes, bug riport

2016-02-12 Thread Crain, Andrew
; which then crashes the program (query window included). >>> >>> >>> >>> This happens rather frustratingly several times a day. >>> >>> >>> >>> Anyone else seeing this? >>> >>> >>> >>> Thanks, >&g

Re: [pgadmin-support] PgAdmin III 1.22 crashes, bug riport

2016-02-04 Thread Dave Page
t;> >> >> >> This happens rather frustratingly several times a day. >> >> >> >> Anyone else seeing this? >> >> >> >> Thanks, >> >> Adam >> >> >> >> From: pgadmin-support-ow...@postgresql.org >

Re: [pgadmin-support] PgAdmin III 1.22 crashes, bug riport

2016-02-04 Thread Strauch, Sheldon
*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 > > > >

Re: [pgadmin-support] PgAdmin III 1.22 crashes, bug riport

2016-02-03 Thread Adam Pearson
...@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

[pgadmin-support] PgAdmin III 1.22 crashes, bug riport

2016-01-26 Thread Lutischán Ferenc
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