Re: PgAdmin III 1.22 crashes, bug riport

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.

On Mon, Feb 15, 2016 at 6:24 AM, Dave Page <dpage(at)pgadmin(dot)org> wrote:

> Hi
>
> On Fri, Feb 12, 2016 at 9:47 PM, Strauch, Sheldon <sstrauch(at)enova(dot)com>
> wrote:
>
>> Hello again Dave,
>>
>> PFA a seg fault dump from pgadmin III 1.22.0 RC 1 debug build.
>>
>> This occurred while resizing a SQL window that had a small explain query
>> in the query edit control and the resulting small explain text result
>> displayed in the result grid. I had previously reset the views on both my
>> SQL window and my main window to "default", closed and restarted pgAdmin as
>> you'd suggested.
>>
>> Clearly, this is happening deep in the bowels of wx and the apple display
>> code. As far as anything odd about my machine goes, I typically run my
>> MacBookPro with two 27" displays, one Thunderbolt, one Cinema, as well as
>> the laptop Retina display. I also regularly use my Apple wireless mouse
>> and wireless keyboard. It is worth noting that I do experience such faults
>> when using only the Retina display, just less frequently.
>>
>>
> That looks like a different issue to the one the first couple of stack
> traces pointed at. It doesn't seem like a particularly unusual
> configuration (I use 2 x 24" Dell monitors over DP connections for
> example), so I suspect that's not the cause. I'll have to poke at that one
> further and see if I can reproduce it.
>
> As for the other issue (the one with GetPort() near the top of the stack
> trace), I've made some tweaks to the code to include a little more sanity
> checking. Could you (and Andrew Crain) give the test build at
> http://developer.pgadmin.org/~dpage/pgadmin3-1.22.1-test.dmg a whirl
> please?
>
> Thanks.
>
>
>> On Fri, Feb 12, 2016 at 11:20 AM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
>>
>>> Thanks. It's not entirely certain as that's obviously not a debug build,
>>> but it does look like that might be the same crash. Now if I can just
>>> figure out how to recreate it...
>>>
>>> On Fri, Feb 12, 2016 at 4:13 PM, Crain, Andrew <
>>> acrain(at)cincinna(dot)gannett(dot)com> wrote:
>>>
>>>> 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" <dpage(at)pgadmin(dot)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 <sstrauch(at)enova(dot)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(dot)Pearson(at)4finance(dot)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-owner(at)postgresql(dot)org
>>>> >>> [mailto:pgadmin-support-owner(at)postgresql(dot)org] On Behalf Of
>>>> Lutischán Ferenc
>>>> >>> Sent: 26 January 2016 9:05 AM
>>>> >>> To: pgadmin-support(at)postgresql(dot)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(at)postgresql(dot)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
>>>> >
>>>>
>>>
>>>
>>>
>>> --
>>> Dave Page
>>> Blog: http://pgsnake.blogspot.com
>>> Twitter: @pgsnake
>>>
>>> EnterpriseDB UK: http://www.enterprisedb.com
>>> The Enterprise PostgreSQL Company
>>>
>>
>>
>>
>> --
>>
>> 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.*
>>
>
>
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>

--

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.*