Bug #52094 "Attempted to read or write protected memory" when click on "Fetch All"
Submitted: 16 Mar 2010 13:30 Modified: 26 Apr 2010 12:36
Reporter: Samir Abboushi Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version:5.2.16 Beta Revision 5249 OS:Microsoft Windows (Vista 64)
Assigned to: CPU Architecture:Any
Tags: memory error

[16 Mar 2010 13:30] Samir Abboushi
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 Recordset.limit_rows(Recordset* , Boolean )
   at MySQL.Grt.Db.Recordset.limit_rows(Boolean value)
   at MySQL.Grt.Db.RecordsetView.limitRowsButton_Click(Object sender, EventArgs e)
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripButton.OnClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   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.ToolStrip.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 if it can be reliably recreated by executing a SQL query, and then clicking "Fetch All"
[16 Mar 2010 13:53] Miguel Solorzano
Thank you for the bug report. What is the size of dataset are you trying to query?. Thanks in advance.
[16 Mar 2010 14:14] Samir Abboushi
The MYD file is almost 10MB.
My query (after clicking on "Fetch All") returns 1710 rows, 5 columns.

I have subsequently clicked on the "Fetch All" button since the error (without rebooting or exiting) and have not experienced further errors.
[26 Mar 2010 12:36] Susanne Ebrecht
Many thanks for writing a bug report.

For making a deeper analysis we need to know exactly what we could do to reproduce this problem.
[26 Apr 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".