MySQL Bugs: #60115: MySQL Workbench crashes at startup on Win7/64-bit

Bug #60115	MySQL Workbench crashes at startup on Win7/64-bit
Submitted:	12 Feb 2011 22:33	Modified:	4 Mar 2011 13:12
Reporter:	Oddbjrn Steen	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	5.2.31 rev7115	OS:	Windows (Win7 64-bit Home Premium(Norwegian))
Assigned to:		CPU Architecture:	Any
Tags:	64bit, crash, startup, win7, workbench

Description:
A few seconds after trying to start program, the message "MySQL Workbench has stopped working" appears and the loading exits. Report.wer log file attached.

How to repeat:
Just try to execute MySQL Workbench from the Start menu or MySQLWorkbench.exe directly.

Suggested fix:
Unknown.

Windows log file from the crash.

Attachment: Report.wer (application/octet-stream, text), 18.59 KiB.

I have the same problem, running Windows 7 64-bit.  Workbench ran fine 2 weeks ago, then suddenly started crashing on startup and I don't see any Windows updates that would have caused this.  Please see my log file below.

I have the same problem, running Windows 7 64-bit.  Workbench ran fine 2 weeks ago, then suddenly started crashing on startup and I don't see any Windows updates that would have caused this.  Please see my log file below.

Log file from crash (& sorry for dup. comments above!)

Attachment: Report.wer (application/octet-stream, text), 21.32 KiB.

Updating to the latest ATI drivers(Radoen HD 5650) resolved the problem.

Same problem, but NVidia video card. Downloading current drivers now, but version i have is only 3 weeks old and this issue happened before i installed those.

Hope someone can find a fix for this. Will also attach the only Event Log entry this crash triggered.

Win7 Event Viewer log

Attachment: mysqlworkbench crash.evtx (application/octet-stream, text), 68.00 KiB.

When you get the crash, right click on the crash dialog (any blank area), then Copy Stacktrace from the menu and paste here. Also include output of Help -> System Info. Thanks

Alfredo:
Not sure what you mean by that. When i try to launch the app, it crashes before it even clears the splash screen. It immediately goes to a Windows system crash notice: "MySQL Workbench has stopped working." etc.

There's no right-click menu available in that dialog, and it's modal over the hanging splash screen. No way to access any stack or other debugging info that i can see. Unless you can clarify further what you mean, the only info i know to provide is the Event Viewer log i've already attached.

Thanks.
-joe

I have ATI Radeon 4650 graphics and I tried updating drivers but was unable to (the upgrade changed the name of the display driver in my device manager and my screen started flickering so I had to revert back) so the solution posted by another user doesn't work for me.

Is anyone looking into this critical issue??

All reporters,

Please, check if starting Workbench with -swrendering option from the cmd.exe command line window solves the problem for you.

If you are still affected and your videocard is different from Radeon HD 5650, please, consider creating separate bug reports. Here we clearly have the case when upgrading drivers solved the problem.

I tried the -swrendering option but get the same error message. 

c:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE>mysqlworkbench.exe -swrender
ing

c:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE>
Unhandled Exception: System.AccessViolationException: Attempted to read or write
 protected memory. This is often an indication that other memory is corrupt.
   at wb.WBContextUI.init(WBContextUI* , WBFrontendCallbacks* , WBOptions* )
   at MySQL.Workbench.WbContext.init(WbFrontendCallbacks callbacks, WbOptions op
tions)
   at MySQL.GUI.Workbench.Program.Main(String[] Args)
mysqlworkbench.exe -swrendering | c:\junk.txt
'c:\junk.txt' is not recognized as an internal or external command,
operable program or batch file.

i don't mean to be argumentative, but i hardly see the benefit of all these reports sharing identical symptoms being submitted as separate bugs. The video driver update "solution" appears to be the exception to this behavior, not the rule. Several different video cards are listed, even by different manufacturers, so either the one person whose problem was solved by updating drivers was lucky, or something else was involved in fixing that problem.

For what it's worth, i will try the command-line at work tomorrow and follow-up.

Just for the record I have ATI Radeon 4650 video card using dual monitor and I don't have that issue (Vista 64-bit).

If upgrading drivers fixed the problem for original poster and not for everyone else, then we have people with at least 2 different problems here. Mixing up both can be very confusing, so if you're still following this, please move on to bug #60248 and post a list of installed software there. Also, install the .NET installation verifier from http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx and post the output to that bug report. I'll close this bug since from the comments from original poster, it was some driver problem. Thanks.

Ok. Feeling more reasonable today. Apologies around. Will move over to the other bug report and continue from there. For the record on this one, command line instructions did not produce any better results or any additional information.

Moving on...

I'm having the same problem and this is what I get when trying to load MySQLWorkbench -swrendering
Unhandled Exception: System.TypeInitializationException: The type initializer for 'ScintillaNet.PageInformation' threw an exception. ---> System.ArgumentException: Font 'Arial' does not support style 'Regular'.

So I downloaded the new version of ScintillaNet - version 2.2 now fixes this Ariel font error.  And now it doesn't even load ('cause the manifest file is looking for version 2 of the ScintillaNet.dll and I can't edit that)
 Maybe a quick recompile with the new version will fix the Windows 7 64 bit problem!!!!  Don't like using HeidiSQL. Thankx.

The possible solution is in here since april, when is this going to be fixed?

See #60248 - as far as i know, the bug has been resolved, as reported by several users. i'm running 5.2.34r7780 successfully. Current version is 5.2.35, so unless there's been a regression, try installing the current version of Workbench:
http://dev.mysql.com/downloads/workbench/

I'm sorry, I overlooked the version number. I'm having this exact problem, not the other issue, on 5.2.35
Do I need fill in another bug thread?

Am getting the same errors with 5.2.35, running on Windows 7 x86_64.
Dual screen layout on a core i5 Lenovo T510 laptop (Intel Video chipset)

Output at command prompt as follows :

C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE>MySQLWorkbench.exe

C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE>
Unhandled Exception: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other
memory is corrupt.
   at wb.WBContextUI.init(WBContextUI* , WBFrontendCallbacks* , WBOptions* )
   at MySQL.Workbench.WbContext.init(AppImpl application, WbOptions options, VoidStrUIFormDelegate create_main_form_view)
   at MySQL.GUI.Workbench.Program.Main(String[] Args)

C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE>MySQLWorkbench.exe -swrendering

C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE>
Unhandled Exception: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other
memory is corrupt.
   at wb.WBContextUI.init(WBContextUI* , WBFrontendCallbacks* , WBOptions* )
   at MySQL.Workbench.WbContext.init(AppImpl application, WbOptions options, VoidStrUIFormDelegate create_main_form_view)
   at MySQL.GUI.Workbench.Program.Main(String[] Args)

I have installed the VC++ 10 re-distributable package (multiple times).

People having crash with a stack trace containing:
 at wb.WBContextUI.init(WBContextUI* , WBFrontendCallbacks* , WBOptions* )
   at MySQL.Workbench.WbContext.init(AppImpl application, WbOptions options,

please file a new bug (or find a bug with the same stack trace), including the log files created by Workbench (...AppData\Roaming\MySQL\Workbench\logs). Not all crashes are the same, even if they all happen at startup. The looks of the stack trace will give a hint whether it's the same bug or not.

What does this mean? I istalled and sucessfully creatad av projekt then it crached, now i just get this error:

Tillämpningsprogram: MySQLWorkbench.exe
Framework-version: v4.0.30319
Beskrivning: Processen avslutades på grund av ett ohanterat undantag.
Undantagsinformation: System.UnauthorizedAccessException
Stack:
   vid System.IO.__Error.WinIOError(Int32, System.String)
   vid System.IO.File.Delete(System.String)
   vid MySQL.GUI.Workbench.Program.RemoveCompiledPythonFiles(System.String)
   vid MySQL.GUI.Workbench.Program.Main(System.String[])

Issue: I have below error during startup on window 7 64 bit

c:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE>
Unhandled Exception: System.AccessViolationException: Attempted to read or write
 protected memory. This is often an indication that other memory is corrupt.
   at wb.WBContextUI.init(WBContextUI* , WBFrontendCallbacks* , WBOptions* )
   at MySQL.Workbench.WbContext.init(WbFrontendCallbacks callbacks, WbOptions op
tions)
   at MySQL.GUI.Workbench.Program.Main(String[] Args)

Solution: this is work for me
 Rename the caused graphics driver dll file 
		File: C:\Windows\SysWOW64\aticfx32.dll 
		Rename: C:\Windows\SysWOW64\aticfx321.dll

Win7 64bit.
MySQL Workbench 64bit v6.3
Needed VS2013 64bit (however I had installed 2010 and 2012 in 32bit and 64bit before it)

This looks to also have the same problem, during install there is an error dialog that appears

It would be much better if the installer does not include (and automatically install) the appropriate Microsoft C++ Redistributable needed that it checked the redistributable was installed on the system.

The MySQL WB installer should have a prerequisite checker and at least warn (and provide Microsoft.com download links to resolve the matter) for the appropriate MSVCRT*.DLLs needed, an option should still exist to skip through the failed pass.