MySQL Bugs: #62023: Random Crashing in MySQL Workbench

Bug #62023	Random Crashing in MySQL Workbench
Submitted:	28 Jul 2011 23:22	Modified:	8 Sep 2011 20:54
Reporter:	E M	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	5.2.34	OS:	Windows (Win 7, 64 bit)
Assigned to:		CPU Architecture:	Any

Description:
Opening sql script causes crash, leading to display of bug reporter. SQL script does NOT open.

How to repeat:
1. Open MySQL workbench
2. Made alterations to EER diagram (added foreign key reference from table a to table b, when a prior link between table a and table b already exists)
3. Switch to "SQL Editor (Local Instance)" tab
4. Select "File"
5. Select "Open SQL Script"
6. Select script from dialog box
7. Select "Open"

At this point the application crash handler is shown

A workaround, prior to step four is:
3a. Select "Database" menu option
3b. Select "Query Database"
3c. Select MySQL 5 stored connection
3d. Click OK

Step 4 onwards work as expected but ONLY if a database connection has been established.

Crash report dialog only states "MySQL Workbench has encountered a problem. External component has thrown an exception"

Suggested fix:
I shouldn't need to establish a database connection to edit SQL scripts.

I suggest that an SQL script should be able to be opened without having to make a database connection, alternatively the application should force me to open a database connection if the intended behavior is to require a database connection. The crash reporter dialog SHOULD NOT be displayed when trying to  edit SQL scripts!

Thank you for the bug report. Could you please provide the output of Help->System Info?. I couldn't repeat on Vista 64-bits. Thanks.

Output from "help"->"system info" as requested...

MySQL Workbench CE for Windows version 5.2.34

Configuration Directory: C:\Users\Monkey\AppData\Roaming\MySQL\Workbench

Data Directory: D:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE

Cairo Version: 1.8.8

Rendering Mode: OpenGL is available on this system, so OpenGL is used for rendering.

OpenGL Driver Version: 3.3.0

OS: Microsoft Windows 7 Ultimate Edition Service Pack 1 (build 7601), 64-bit

CPU: 2x Intel(R) Core(TM)2 Duo CPU     P7450  @ 2.13GHz, 4.0 GiB RAM

Active video adapter: NVIDIA GeForce GT 240M       

Installed video RAM: 1024 MB

Current video mode: 1920 x 1080 x 4294967296 colors

Used bit depth: 32

Driver version: 8.17.12.7533

Installed display drivers: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um

Current user language: English (United Kingdom)

How did you open an unconnected SQL Editor tab?
Also, when the error dialog appears, right click on the area below the icon in that window, select Copy Stack Trace in the context menu and paste it to this bug report. 
Thanks

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".