| From: | Akshay Joshi <akshay(dot)joshi(at)enterprisedb(dot)com> |
|---|---|
| To: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Fixed crash in execution dialog |
| Date: | 2013-07-26 07:53:51 |
| Message-ID: | CANxoLDdqCSTQ1K5KoAyH-r5cJsJf+a-5tmVPLkj-0ybEmYHX9Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
Hi Dave
Today I have fixed one crash in execution dialog. The bug is reproducible
by performing following steps:
1. Connect to any database server.
2. Right click on the database(big in size) and select maintenance.
3. Start taking maintenance and click the cancel button.
4. After clicking on cancel, immediately click on cross (x) button.
With the above steps Abort() function gets called twice on from cancel
event and another from close event. Attached is the patch file. Please
review it and if it looks good to you then can you please commit it.
--
*Akshay Joshi
Senior Software Engineer
EnterpriseDB Corporation
The Enterprise PostgreSQL Company
Phone: +91 20-3058-9522
Mobile: +91 976-788-8246*
| Attachment | Content-Type | Size |
|---|---|---|
| Execution_Dialog_Crash.patch | application/octet-stream | 2.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2013-07-26 12:57:04 | pgAdmin III commit: Keep better track of when external process threads |
| Previous Message | Akshay Joshi | 2013-07-24 06:48:34 | Re: pgAdmin Event Trigger Compatibility |