Bug #64297 SQL Workbench enters a hard run state at exit
Submitted: 10 Feb 2012 20:09 Modified: 27 Mar 2012 17:20
Reporter: William Lipman Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Workbench: SQL Editor Severity:S1 (Critical)
Version:5.2.37 CE OS:Windows (Win XP Pro SP3)
Assigned to: CPU Architecture:Any
Tags: Hard Run, Program Exit, System Freezes

[10 Feb 2012 20:09] William Lipman
On more than one occasion I have found that when SQL Editor has been open and not used for a moderate period, while all query Windows have been saved, if I then exit SQL Workbench my Windows XP Pro O/S goes into a hard run state where I can not switch to any other program, including task manager.

In short, the Windows system freezes. However, since I suspected that the problem was inside SQL Workbench, and that it was in some sort of loop associated to the network session with the remote MySQL Server instance, I decided to disconnect the network cable and found that SQL Workbench terminated. 

At that point, all other applications continued to run, although, of course, I got the "A network cable is disconnected" mesage from Windows. But all evidence seems to point to SQL Workbench being the culprit.

How to repeat:
This has happened at least three times in my brief experience with SQL Workbench over the last thirty days, but as it happens only a shutdown time, I am not sure how to replicate the problem. 

It might replicate if one were to open an SQL Editor window to a remote server, perform a query, save the file and then leave the window open for an hour or two, followed by closing the main application window.
[13 Feb 2012 18:16] MySQL Verification Team
Thank you for the bug report. Have you monitored with the Windows Task Manager the memory usage while the application is idle?.
[13 Feb 2012 19:43] Rafael Antonio Bedoy Torres
Please, try to start Workbench from cmd.exe command line client with extra
-log-level=debug3 option. Send the output and content of wb.log file.

Thanks in advance!
[13 Feb 2012 19:58] William Lipman
A possible clue to what is happening at Workbench shutdown is as follows. I just shut down Workbench after it had been running several hours. Before doing so, I launched Task Manager.

Task Manager showed that Workbench was consuming close to 100% of resources for about three to five seconds. No other program or process was busy at that time, so it was just Workbench using the processor. Is this behavior normal?
[27 Feb 2012 17:20] Valeriy Kravchuk
Also it makes sense to upgrade to 5.2.38 if you plan to test this further...
[28 Mar 2012 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".