MySQL Bugs: #59745: Both CE and SE always throw error dialog about 2-3 seconds after shutting down.

Bug #59745	Both CE and SE always throw error dialog about 2-3 seconds after shutting down.
Submitted:	26 Jan 2011 15:45	Modified:	28 Feb 2011 16:53
Reporter:	Karl Nicoletti	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S3 (Non-critical)
Version:	5.2.31 build 7110, 5.2.31a build 7115	OS:	Windows (Windows XP Pro Version 2002 SP3)
Assigned to:		CPU Architecture:	Any
Tags:	Error on Exit, windows, workbench

Description:
Exiting from either the CE or SE versions of MySQL Workbench results in an error dialog being displayed approximately 2-3 seconds after the application closes all of its windows and appears to shut down.

Does not appear to corrupt any data in the model. Just a scary message.

Does not happen in models created from scratch in 5.32.31.

How to repeat:
1) Save a model.
2) Select File->Exit.

MySQL Workbench closes all its windows. Everything appears normal, then about 2-3 seconds up pops the following dialog:

"MySQL Workbench has encountered a problen and needs to close. We are
sorry for the inconvenience.

If you were in the middle of something, the information you were working on might be lost."

The model appears to be intact when reopening the model, it appears intact.

Hi Karl,
can you check if this is still the case with 5.2.31a (currently available on our download-pages)?
if so, please attach the output of help-›system info
thanks in advance

OUTPUT from Help->System Info:

MySQL Workbench CE for Windows version 5.2.31
Configuration Directory: C:\Documents and Settings\KNICOLET\Application Data\MySQL\Workbench
Data Directory: C:\Program Files\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 XP Professional Service Pack 3 (build 2600)
CPU: 2x Intel(R) Core(TM)2 Duo CPU     P8700  @ 2.53GHz, 3.0 GiB RAM
Active video adapter: NVIDIA Quadro NVS 150M
Installed video RAM: 512 MB
Current video mode: 1280 x 1024 x 4294967296 colors
Used bit depth: 32
Driver version: 6.14.12.6099
Installed display drivers: nv4_disp.dll
Current user language: English (United States)

I see this for older 5.2.31 releases (build 7102, for example), but had you check with 5.2.31a (build 7115) as requested?

Yes. Downloaded the installer according to directions, loaded model, changed something in it, saved model, exit MWB, get Jave exception. If you look at the note [22 Feb 22:54], this is the output from Help->System Info as you requested earlier.  Looks like the About screen didn't have the "a" after the 5.2.31. See the attached MWB_5.2.31a_aboutscreen.jpg.

About/Splash screen from MWB 5.2.31a (Revision 7110)

Attachment: MWB_5.2.31a_aboutscreen.jpg (image/jpeg, text), 27.02 KiB.

OK. I made absolutely sure to download the mysql-workbench-gpl-5.2.31a-win32.msi file, installed, loaded model, changed something, saved, exited and 2 seconds later get the Java exception dialog. See latest MWB_5.2.31a-7115aboutscreen.jpg for the about screen capture.

Here is the Help->System Info....

MySQL Workbench CE for Windows version 5.2.31
Configuration Directory: C:\Documents and Settings\KNICOLET\Application Data\MySQL\Workbench
Data Directory: C:\Program Files\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: 2.1.2
OS: Microsoft Windows XP Professional Service Pack 3 (build 2600)
CPU: 2x Intel(R) Core(TM)2 Duo CPU     P8700  @ 2.53GHz, 3.0 GiB RAM
Active video adapter: NVIDIA Quadro NVS 150M
Installed video RAM: 512 MB
Current video mode: 1280 x 1024 x 4294967296 colors
Used bit depth: 32
Driver version: 6.14.11.7590
Installed display drivers: nv4_disp.dll
Current user language: English (United States)

About/Splash screen from MWB 5.2.31a (Revision 7115)

Attachment: MWB_5.2.31a-7115aboutscreen.jpg (image/jpeg, text), 26.14 KiB.

Don't worry about this anymore. I forward engineered the model into a database, reverse engineered it back into a new model, and manually recreated the diagrams I needed. No more problem on shutdown. I did lose all my inserts and diagrams, however. Too bad there is no easy way to dump these out and reload them into a new model.

I might as well close this for you, since you guys seem really swamped with important work.