| Bug #2537 | Close query window while executing causes crash | ||
|---|---|---|---|
| Submitted: | 27 Jan 2004 14:47 | Modified: | 27 Jan 2004 14:55 |
| Reporter: | Julian Chappell | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQLCC | Severity: | S3 (Non-critical) |
| Version: | 0.94 | OS: | Windows (Windows 2000) |
| Assigned to: | Assigned Account | CPU Architecture: | Any |
[27 Jan 2004 14:55]
Dean Ellis
Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely to be the same. Because of this, we hope you add your comments to the original bug instead. Thank you for your interest in MySQL. Additional info: This is a duplicate of bug #2407.
Description: Hi, When you have the list of tables showing in the tree view on the LH side of the screen, if you double click a table to view all rows and then close the window while the query is still executing (as in "oops i meant to edit the table definition, not view the contents") you'll get a crash with what looks like a dodgy pointer ("instruction at 0x...referenced memory at 0x2d") and sometimes something strange about an INT 3 as well. How to repeat: Double click table to view all rows then close window while query is still executing. Suggested fix: Get some coffee and your best coding trousers on ;-)