MySQL Bugs: #58717: Moving table object on ER diagram causes crash

Bug #58717	Moving table object on ER diagram causes crash
Submitted:	3 Dec 2010 18:52	Modified:	26 Jan 2011 20:40
Reporter:	Andre Marion	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S2 (Serious)
Version:	5.2.30	OS:	Windows (Windows 7 Enterprise 64bit)
Assigned to:		CPU Architecture:	Any
Tags:	crash, EER Diagram, workbench

Description:
I was moving a table object inside the ER diagram when it crashed.

I have no more details than that and this is the first time it has happened so I don't know if it will be re-creatable.

I can't get out of the Unexpected error window as each time I keep closing it, it simply re-appears. Appears to be an endless loop.

I have to Force Quit the entire application to be able to continue with the application.

*** Dialog box text ***

Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

We are sorry for the inconvenience but an unexpected exception has been raised by one of the MySQL Workbench modules. In order to fix this issue we would kindly ask you to file a bug report. You can do that by pressing the [Report Bug] button below. 

Please make sure to include a detailed description of your actions that lead to this problem.

Thanks a lot for taking the time to help us improve MySQL Workbench!

The MySQL Workbench Team

How to repeat:
Don't know how to repeat. I was simply working on my EER diagram and moving table objects around when it crashed.

As mentioned, this is the first crash of this nature, so I don't know if it will happen again.

If crash like this will ever happen again, please, right click somewhere in the dialog box with no text in it and then select the Copy stack trace to clipboard option. Please, attach what you get to this bug.

Here's the stack trace (this time I had just removed a foreign key relationship and was attempting to add it back in by clicking on the "Place a relationship Using Existing Columns" and then clicking on the first table causes the crash:

Exception = System.AccessViolationException
Message = Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
FullText = System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
   at wb.ModelDiagramForm.handle_mouse_button(ModelDiagramForm* , MouseButton , Boolean , Int32 , Int32 , EventState )
   at MySQL.Workbench.ModelViewForm.OnMouseUp(MouseEventArgs e, Int32 X, Int32 Y, Keys keystate, MouseButtons buttons)
   at MySQL.GUI.Workbench.ModelDiagramForm.CanvasPanel_MouseUp(Object sender, MouseEventArgs e)
   at System.Windows.Forms.Control.OnMouseUp(MouseEventArgs e)
   at MySQL.Utilities.WindowsCanvasViewerPanel.OnMouseUp(MouseEventArgs e)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Please, check if the same problem happens with a newer version, 5.2.31. Send the output of Help > System Info menu item also.

Just updated to the latest version 5.2.31a and was updating my model. I removed a couple of foreign key references, saved it, synchronized the database. Then I deleted a cross reference table that I no longer needed, saved the model, then synchronized the database. Then I clicked on another table images and wanted to re-position it in the model and CRASH! I couldn't break out of the crash either, the dialog box kept popping up. Had to force quit the app.

Here's the stack:

Exception = System.AccessViolationException
Message = Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
FullText = System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
   at wb.ModelDiagramForm.handle_mouse_button(ModelDiagramForm* , MouseButton , Boolean , Int32 , Int32 , EventState )
   at MySQL.Workbench.ModelViewForm.OnMouseDown(MouseEventArgs e, Int32 X, Int32 Y, Keys keystate, MouseButtons buttons)
   at MySQL.GUI.Workbench.ModelDiagramForm.CanvasPanel_MouseDown(Object sender, MouseEventArgs e)
   at System.Windows.Forms.Control.OnMouseDown(MouseEventArgs e)
   at MySQL.Utilities.WindowsCanvasViewerPanel.OnMouseDown(MouseEventArgs e)
   at System.Windows.Forms.Control.WmMouseDown(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Output of Help -> System Info:

MySQL Workbench CE for Windows version 5.2.31
Configuration Directory: C:\Users\andre.marion\AppData\Roaming\MySQL\Workbench
Data Directory: C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE
Cairo Version: 1.8.8
Rendering Mode: OpenGL is available on this system, so OpenGL is used for rendering.
OpenGL Driver Version: 2.0.0 - Build 8.14.10.1930
OS: Microsoft Windows 7 Enterprise Edition (build 7600), 64-bit
CPU: 2x Intel(R) Core(TM)2 CPU          6300  @ 1.86GHz, 3.9 GiB RAM
Active video adapter: Intel(R)  G965 Express Chipset Family
Installed video RAM: 384 MB
Current video mode: 1680 x 1050 x 4294967296 colors
Used bit depth: 32
Driver version: 8.15.10.1930
Installed display drivers: igdumd64.dll,igdumdx32
Current user language: English (United States)

Please try starting WB with the -swrendering cmdline option

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".