MySQL Bugs: #52808: MySQL Workbench 5.2.18 will not load

Bug #52808	MySQL Workbench 5.2.18 will not load
Submitted:	14 Apr 2010 7:02	Modified:	18 Apr 2010 16:42
Reporter:	Peter Brookes-Smith	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	5.2.18	OS:	Windows (xp pro)
Assigned to:		CPU Architecture:	Any

Description:
I installed 5.2.18 last night on my laptop. Initially, it worked fine but when I came out and then restarted, it would not load and fell over. 

This morning, I installed it onto my desktop machine (both are xp) it would not load at all and just fell over.

Windows threw out a report error screen and i was able to copy the error signature below:

EventType : clr20r3     P1 : mysqlworkbench.exe     P2 : 5.2.18.5625     
P3 : 4bc42a47     P4 : mysqlcsutilities     P5 : 1.0.0.0     P6 : 4bc42682     
P7 : 59     P8 : 26     P9 : system.exception

How to repeat:
Install 5.2.1.8 and try to run it on windows xp box

Hi Peter,

could you provide the information shown when you go to help->System information inside WB?
you can also try to launch Workbench with the cmd-line-parameter -swrendering.
thanks in advance

I have removed 5.2.18 from my desktop as it would not load at all.

It still won't load on laptop but I can leave it installed for a while.

I tried the -swrendering but this made no difference.

It still fell over and the error signature seemed the same as before.

I have been getting same error, 

------------------------------------------
  Navn på problemhændelse:	CLR20r3
  Problemsignatur 01:	mysqlworkbench.exe
  Problemsignatur 02:	5.2.18.5625
  Problemsignatur 03:	4bc42a47
  Problemsignatur 04:	MySQLCsUtilities
  Problemsignatur 05:	1.0.0.0
  Problemsignatur 06:	4bc42682
  Problemsignatur 07:	59
  Problemsignatur 08:	26
  Problemsignatur 09:	System.Exception
  OS-version:	6.0.6002.2.2.0.256.1
  Landestandard-id:	1030
------------------------------------------

for my experiance it happens for me if i try to open a ".mwb" by clicking it direct.

but works fine if i openthe ".mwb" once the app is already open

Had exact same error at my work pc as well but i don't have access to the system info for that one right now (all tho i submit it earlier for another error with zooming)

---------------------------------------
MySQL Workbench SE for Windows version 5.2.18
Cairo Version: 1.8.8
Rendering Mode: OpenGL is not available on this system, INTERNAL ERROR, contact the authors.
OpenGL Driver Version: Not Detected
OS: Microsoft Windows Vista Ultimate Edition Service Pack 2 (build 6002), 64-bit
CPU: 4x Intel(R) Core(TM)2 Quad CPU           @ 2.66GHz, 8.0 GiB RAM
Video adapter info:
Adapter type: NVIDIA GeForce 8800 GTX
Chip Type: GeForce 8800 GTX
BIOS String: Version 60.80.13.0.0
Video Memory: 786432 KB
---------------------------------------

not sure if revelant, but the one at work had this message also:
---------------------------------------
Rendering Mode: OpenGL is not available on this system, INTERNAL ERROR, contact the authors.
OpenGL Driver Version: Not Detected
---------------------------------------

-Thanks

The situation here is much worse.
MySQL Workbench causes my pc restarted.

I rolled back to 5.2.17.
System Info

MySQL Workbench OSS for Windows version 5.2.17
Cairo Version: 1.8.8
Rendering Mode: OpenGL is not available on this system, INTERNAL ERROR, contact the authors.
OpenGL Driver Version: Not Detected
OS: Microsoft Windows XP Professional Service Pack 2 (build 2600)
CPU: 2x Intel(R) Pentium(R) 4 CPU 3.00GHz, 2.0 GiB RAM
Video adapter info:
Adapter type: Intel(R)  Q965/Q963 Express Chipset Family
Chip Type: Intel(R) GMA 3000
BIOS String: Intel Video BIOS
Video Memory: 262144 KB

I have it set to automatically open the last model file used. 

Based on othercomments that the same thing happens if they double click on a model file but that it is ok if they launch normally, I would say this is very significant.  

Can i edit a file to stop it opening automatically?

If this crash happens only when you double click on .mwb file to open it, then it is likely Bug #52851 that I've just verified. Please, confirm.

5.2.19 seems to have fixed this.

Thanks very much.