From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | <mike(at)thegodshalls(dot)com> |
Cc: | <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: v6 beta 2 still crashes at times whenviewing table results directly |
Date: | 2006-10-12 11:31:07 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E40176D4FB@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
> -----Original Message-----
> From: Mike G [mailto:mike(at)thegodshalls(dot)com]
> Sent: 11 October 2006 20:46
> To: Dave Page
> Cc: pgadmin-support(at)postgresql(dot)org
> Subject: Re: [pgadmin-support] v6 beta 2 still crashes at
> times whenviewing table results directly
>
> Dump attached.
>
Hi Mike,
I've found a couple of issues that might be causing this...
The first was that the edit grid was allowing the refresh button to be
pressed at will, which meant it was possible to start a second refresh
whilst the first query thread was still running. I could reproduce this
by simply banging F5 a few times without waiting for the previous data
load to end. I've fixed this by locking out all methods of refreshing
until the previous call (which may be the initial data load) has
completed.
The second issue would have affected the Query Tool as well, so may be
what Harald was seeing. Essentially, the pgQueryThread class was calling
logging functions in it's query thread which does not appear to be safe.
I've moved all logging so it's in the main app thread and could no
longer reproduce this issue (though I couldn't exactly reproduce it at
will previously, so that isn't proof I've actually fixed it).
These changes will be in the upcoming beta 3.
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | George Pavlov | 2006-10-12 21:22:54 | pgAdmin 1.6 Beta 2 query crashes on windows |
Previous Message | Mike G | 2006-10-11 19:46:00 | Re: v6 beta 2 still crashes at times whenviewing table results directly |