On Mon, Jan 25, 2016 at 9:40 AM, Regina Obe <lr@pcorp.us> wrote:
>> -----Original Message-----
>> From: Dave Page [mailto:dpage@pgadmin.org]
>> Sent: Monday, January 25, 2016 4:11 AM
>> To: Regina Obe <lr@pcorp.us>
>> Cc: pgAdmin Support <pgadmin-support@postgresql.org>
>> Subject: Re: [pgadmin-support] pgAdmin v1.22.0 keeps freezing and crashing
>
>> On Sat, Jan 23, 2016 at 8:49 PM, Regina Obe <lr@pcorp.us> wrote:
>> I'm running Windows 7 64-bit and had recently upgraded to pgAdmin v1.22.0.
>> It seems though that quite frequently when I run a long-running query,
>> pgAdmin freezes.
>
>> Does you machine go to sleep or anything like that when it crashes?
> No
>
>>> I've since been forced to downgrade back to pgAdmin 1.20.
>>>
>>> My husband has the same issue on his computer, though could be how we
>>> have our setups configured in a similar way.
>>>
>>> I did talk to someone else who said when she was running the PostGIS
>>> shp2pgsql-gui plugin on v1.22.0 it would crash (windows 7 32-bit), so
>>> she reverted too back to v1.20 and problem went away.
>
>> Oh? The plugins are simply tools that are launched in their own processes - and that code hasn't changed since 1.20.
Doesit crash immediately? Is it pgAdmin or the plugin that crashes?
>
> Well the postgis-gui plugin is compiled with mingw64 and is the one distributed with PostGIS 2.2 one (not that it
matterssince that code has not changed in a while).
> I have to test this myself. My friend was using a Windows 7 32-bit and the screen she showed me, it gave some sort
ofVC++ debug error before it crashed (so doesn't seem like it is crashing in the plugin though the error does suggest
that)
> As I recall, I think she got as far as the PostGIS-GUI (shp2pgsql-gui) showing her the list of tables and it was when
sheproceeded to export was when it crashed.
> Again I'll have to check this for myself, since she only sent me a screen shot. Attached is the screen shot she sent
me. She said when she uninstalled 1.22 and reinstalled 1.20 things were okay.
> I usually just use the shp2pgsql command line since it's more efficient for larger tables and I can script it.
Ahh, well that crash is clearly not in the pgAdmin code. Could
shp2pgsql be using pgAdmin's libpq and related libraries?
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company