Bug #54781 | Attempt to read/write protected memory | ||
---|---|---|---|
Submitted: | 24 Jun 2010 14:38 | Modified: | 28 Jun 2010 20:22 |
Reporter: | Kerry Kurtz | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench: SQL Editor | Severity: | S2 (Serious) |
Version: | 5.2.22 CE Revision 6091 | OS: | Windows (XP Pro SP3) |
Assigned to: | CPU Architecture: | Any | |
Tags: | access fault, OSS, query browser |
[24 Jun 2010 14:38]
Kerry Kurtz
[24 Jun 2010 14:39]
Valeriy Kravchuk
Please, check if this ever happens with a newer version, 5.2.24.
[24 Jun 2010 18:07]
Kerry Kurtz
After the fault the output tab/pane has a big red X. The only way of recovering is to shut down and start back up but since the query is still (apparently) running do not know what has been missed or had errors or ?
[25 Jun 2010 7:13]
Valeriy Kravchuk
I've seen that "big red X" several times in the past, but had you tried to get it with 5.2.24, as suggested?
[28 Jun 2010 20:22]
Kerry Kurtz
After testing for about 50,000 queries with 5.2.24 did not have the problem recur with the big red x in the output tab/pane. One comment though, the performance in processing these queries totally stunk. Even though each query (simple replace queries) was indicated as having used less than 10 milliseconds the queries would only be submitted about 1 or 2 per second. The drawing of the output kept it so busy that it took more than 5 seconds for a click on the stop/interrupt button to be recognized.