Bug #51916 Attempt to read/write protected memory
Submitted: 10 Mar 2010 15:05 Modified: 19 May 2010 13:28
Reporter: CPK Smithies Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S2 (Serious)
Version:5.2.16 Rev5249 OS:Microsoft Windows (XP SP3)
Assigned to: CPU Architecture:Any

[10 Mar 2010 15:05] CPK Smithies
Description:
Occurred in reaction to a UI event. I was adding relationships to existing fields on the EER diagram. Dump info:

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:
Don't know how to repeat except to try adding relationships to existing fields on an EER diagram.
[28 Mar 2010 12:29] Valeriy Kravchuk
Thank you for the problem report. What exact data types referencing and referenced columns have?
[31 Mar 2010 4:02] CPK Smithies
The link types were:

SMALLINT(3) /* in one case */
CHAR(30) /* mostly */
VARCHAR(30/40) /* in one case */

Yes, in one case, the referencing link was VARCHAR(40) whilst the referenced primary key was VARCHAR(30).

Hope this helps!
[31 Mar 2010 4:10] CPK Smithies
Oh and I should note that on a subsequent edit, the EER diagram was completed OK, despite the mismatch in referencing/referenced types.
[19 Apr 2010 13:28] Valeriy Kravchuk
Please, check if this problem is repeatable with a newer version, 5.2.19.
[19 May 2010 23: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".