MySQL Bugs: #52634: System crash when restarting up after close

Bug #52634	System crash when restarting up after close
Submitted:	6 Apr 2010 21:09	Modified:	8 Apr 2010 15:52
Reporter:	Michael Zeman	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	5.2.17 OSS rev 5565	OS:	Windows (XP SP3)
Assigned to:		CPU Architecture:	Any

Description:
Workbench causes a system crash when restarting.  Entire system will reboot and, upon logging back in to Windows XP a box pops up that states:

"The system has recovered from a serious error.  A log of this error has been created.

Error signature:

BCCode : 1000008e     BCP1 : C0000005     BCP2 : BF93A34E     BCP3 : A7FAA8C0
BCP4 : 00000000     OSVer : 5_1_2600     SP : 3_0     Product : 256_1     "

I have 3 files in the microsoft crash log:  manifest.txt, Mini040610-02.dmp, and sysdata.xml.  I can attach these if necessary.

How to repeat:
1. Start Workbench
2. Close Workbench (file->exit or click the window X)
3. Start Workbench again

The blue splash page will display followed by the screen going black and the system rebooting.

Suggested fix:
Make it stop crashing the system. :)

Work around is to not shut Workbench off, or to reboot in-between launches of Workbench.  Neither are very good work arounds, however.

I was advised that WB doesn't have any sort of logging system built in, but that it reports out to STDERR and STDOUT, so I ran the following on my Windows XP command line:

MySQLWorkbench.exe > wblog.log 2>&1

I started workbench and then exited out of it (since it only crashes after the second launch), and the log file had the following information in it:

"** (MySQLWorkbench.exe:4040): WARNING **: Plugin 'wb.tools.quickTables' from module WbTools has invalid type ''
** Message: unhandled message 4: wb.file.exit finished in 0.02s

'import site' failed; use -v for traceback"

I ran the same script, had the system crash, but no log was generated.

It's a driver issue.  Intel onboard graphics driver 915G doesn't handle the openGL very well.  Running Workbench with OpenGL turned off ("MySQLWorkbench.exe -swrendering") launches it without crashing.  Better solution - Get a graphics card and stop using crappy onboard graphics.  :)