Bug #52594 Swapped from workbench to another app and back, possibly caused Exception
Submitted: 5 Apr 2010 11:22 Modified: 8 May 2010 16:06
Reporter: Glen Jones Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.2 OS:Microsoft Windows
Assigned to: CPU Architecture:Any

[5 Apr 2010 11:22] Glen Jones
Description:
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)

How to repeat:
did not try
[8 Apr 2010 16:06] Johannes Taxacher
Hi Glen,

do you instructions on how to repeat the problem?
thanks in advance
[8 Apr 2010 16:07] Johannes Taxacher
what exact version are you using?
[8 May 2010 23:01] 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".