Bug #68567 | MySQLWorkbench.exe, version: 5.2.47.10398 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: | 5.2.47.10398 | OS: | Windows (server 2008 r2) |
Assigned to: | CPU Architecture: | Any | |
Tags: | crash windows server 2008 r2, mysqlworkbench |
[5 Mar 2013 1:51]
Paul Leo
[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> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2013-03-05T02:14:21.000000000Z" /> <EventRecordID>13963</EventRecordID> <Channel>Application</Channel> <Computer>HSSCDPHPANCADM.dhss.ak.local</Computer> <Security /> </System> - <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> </EventData> </Event>
[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".