Bug #68567 MySQLWorkbench.exe, version: multi crashes on win server 2008 r2
Submitted: 5 Mar 2013 1:51 Modified: 22 Jul 2013 3:07
Reporter: Paul Leo Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Workbench: SQL Editor Severity:S1 (Critical)
Version: OS:Microsoft Windows (server 2008 r2)
Assigned to: CPU Architecture:Any
Tags: crash windows server 2008 r2, mysqlworkbench

[5 Mar 2013 1:51] Paul Leo
I have had multiple crashes on MYSQLWorkbench. (5 in under 20 minutes)
It seems to happen when I attempt to invoke the query screen

Here is the info from the windows server event log

Faulting application name: MySQLWorkbench.exe, version:, time stamp: 0x511d76f0
Faulting module name: grt.dll, version:, time stamp: 0x511d6840
Exception code: 0xc0000005
Fault offset: 0x00001a88
Faulting process id: 0x64c
Faulting application start time: 0x01ce193a283aad73
Faulting application path: C:\Program Files (x86)\MySQL\MySQL Workbench CE 5.2.47\MySQLWorkbench.exe
Faulting module path: C:\Program Files (x86)\MySQL\MySQL Workbench CE 5.2.47\grt.dll
Report Id: 8c9d3693-852d-11e2-87f8-005056946176

Each of the reports mentions grt.dll

How to repeat:
I will attempt describe at least one of the ways I have seen it crash
1 - start the application - the full screen workbench central comes up
2 - Doublelick on a connection under open connection to start querying under sql dev
3 - the dialog box comes up prompting for password - ( am using root  and standard tcpip connection to localhost
4 - enter password
5 - receive the message sql editor starting or something like that
6 - the main work bend central page comes back up 
7 - lower left says connection cancelled
8 - try selecting query database
9 - select localhost root connection, default mysql schema
10 - enter password - 

If I choose server admin - that comes up fine with same root user and password
once in the sys admin screen - 
once I started again -
I created a new connection, left schema blank, tested and int works.
if I select database from the menu, then query database, use the new stored connection whish is localhhost root - - no default schema, click okay, 
 I get the starting the sql editor
connecting shows at the bottom
I'm prompted for a password, I enter it,
get the opening sql editor again
then it crashes

This is a new install of MySQL 5.6 - am running via rdp
Have a windows server with mysql 5.5 and workbench 5.2 and it is working flawlessly via same rdp
[5 Mar 2013 1:54] Paul Leo
It actually is a showstopper for me!
[5 Mar 2013 2:28] Paul Leo
I reinstalled - I know I should have/could have waited for a reply....
This time I don't even get an error message workbench just closes down
But I noticed in reviewing windows error logs there are some .net runtime errors associated with workbench - I a consultant installing web based applications which use mysql as a db - I checked windows update, and it says everything is uptodate, but am not sure if all updates are being applied - i will attempt to check into that - anyway - here is the net runtime error from the event log

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name=".NET Runtime" /> 
  <EventID Qualifiers="0">1026</EventID> 
  <TimeCreated SystemTime="2013-03-05T02:14:21.000000000Z" /> 
  <Security /> 
- <EventData>
  <Data>Application: MySQLWorkbench.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.AccessViolationException Stack: at <Module>.mforms.MenuItem.callback(mforms.MenuItem*) at MySQL.Forms.MenuItemImpl.menuItemClick(System.Object, System.EventArgs) at System.Windows.Forms.ToolStripItem.RaiseEvent(System.Object, System.EventArgs) at System.Windows.Forms.ToolStripMenuItem.OnClick(System.EventArgs) at System.Windows.Forms.ToolStripItem.HandleClick(System.EventArgs) at System.Windows.Forms.ToolStripItem.HandleMouseUp(System.Windows.Forms.MouseEventArgs) at System.Windows.Forms.ToolStripItem.FireEventInteractive(System.EventArgs, System.Windows.Forms.ToolStripItemEventType) at System.Windows.Forms.ToolStripItem.FireEvent(System.EventArgs, System.Windows.Forms.ToolStripItemEventType) at System.Windows.Forms.ToolStrip.OnMouseUp(System.Windows.Forms.MouseEventArgs) at System.Windows.Forms.ToolStripDropDown.OnMouseUp(System.Windows.Forms.MouseEventArgs) at System.Windows.Forms.Control.WmMouseUp(System.Windows.Forms.Message ByRef, System.Windows.Forms.MouseButtons, Int32) at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef) at System.Windows.Forms.ScrollableControl.WndProc(System.Windows.Forms.Message ByRef) at System.Windows.Forms.ToolStrip.WndProc(System.Windows.Forms.Message ByRef) at System.Windows.Forms.ToolStripDropDown.WndProc(System.Windows.Forms.Message ByRef) at System.Windows.Forms.Control+ControlNativeWindow.OnMessage(System.Windows.Forms.Message ByRef) at System.Windows.Forms.Control+ControlNativeWindow.WndProc(System.Windows.Forms.Message ByRef) at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr) at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef) at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32) at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext) at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext) at System.Windows.Forms.Application.Run(System.Windows.Forms.ApplicationContext) at MySQL.GUI.Workbench.Program.Main(System.String[])</Data> 
[5 Mar 2013 2:41] Paul Leo
I did verify that all available updates have been applied
[5 Mar 2013 3:13] Paul Leo
I am able to access the Mysql db on the machine where workbench is not able to access the db, working from another machine using mysql workbench v 5.2.34 CE revision 7780
[22 Jun 2013 3:07] Alfredo Kojima
What happens if you rename the Users\<you>\AppData\Roaming\MySQL\Workbench directory?
If that fixes the problem, could you zip it send us the contents? If it contains sensitive info, maybe the wb_state.xml and wb_options.xml files are enough (try copying back these to see if the crash happens again). Thanks
[23 Jul 2013 1:00] Bugs System
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".