Bug #64212 Crashed attempting to open a second query tab
Submitted: 2 Feb 2012 17:44 Modified: 2 Mar 2012 18:13
Reporter: Glenn Botts Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version:5.2.33 CE OS:Windows (Windows 7 64-bit)
Assigned to: CPU Architecture:Any
Tags: crash

[2 Feb 2012 17:44] Glenn Botts 
Description:
The workbench didn't close, but the error message said that it encountered an error and needed to restart.

I was attempting to open a second query tab, so I could play with the SQL string in the primary query window. Instead I opened a new database connect, which I tried to close while it was still starting up. I got an error/crash for my troubles.

How to repeat:
After I got the initial error, clicking on the left toolbar icon for "Create a new Scratch Area for executing queries" will generate the same error dialog.
[2 Feb 2012 17:47] Glenn Botts 
It's possible that this was causing by running low on RAM while the program was starting. TomCat was hogging 1.6GBs of my 4GBs of RAM. I closed TomCat while the Workbench was loading.
[2 Feb 2012 18:13] Valeriy Kravchuk 
Please, check if this crash still happens with a newer version, 5.2.37.
[3 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".