Bug #55406 Attempted to read or write protected memory.
Submitted: 20 Jul 2010 16:22 Modified: 20 Aug 2010 16:30
Reporter: Alberto Arze-Aguirre Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Workbench: Modeling Severity:S2 (Serious)
Version: OS:Windows (XP)
Assigned to: CPU Architecture:Any

[20 Jul 2010 16:22] Alberto Arze-Aguirre
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 bec.FKConstraintColumnsListBE.set_column_is_fk(FKConstraintColumnsListBE* , NodeId* , Boolean )
   at MySQL.Grt.Db.FKConstraintColumnsListBE.set_column_is_fk(NodeId node, Boolean flag)
   at MySQL.GUI.Workbench.Plugins.DbMysqlTableFkColumnListModel.ValuePushed(Object sender, NodeControlValueEventArgs e)
   at Aga.Controls.Tree.NodeControls.BindableControl.OnValuePushed(NodeControlValueEventArgs args)
   at Aga.Controls.Tree.NodeControls.BindableControl.SetValue(TreeNodeAdv node, Object value)
   at Aga.Controls.Tree.NodeControls.NodeCheckBox.SetCheckState(TreeNodeAdv node, CheckState value)
   at Aga.Controls.Tree.NodeControls.NodeCheckBox.MouseDown(TreeNodeAdvMouseEventArgs args)
   at Aga.Controls.Tree.TreeViewAdv.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.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:
I was trying to set a foreign key in a child table pointing to a parent table
[20 Jul 2010 16:30] Valeriy Kravchuk
What exact version of MySQL Workbench do you use?
[20 Aug 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".