MySQL Bugs: #52951: When Deleting More Than 200 Records A Write Protected Memory Error Occurs

Bug #52951	When Deleting More Than 200 Records A Write Protected Memory Error Occurs
Submitted:	19 Apr 2010 17:59	Modified:	26 Apr 2010 14:05
Reporter:	Paul Rudge	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S2 (Serious)
Version:	5.2.19 Beta	OS:	Windows (XP SP3)
Assigned to:	Sergei Tkachenko	CPU Architecture:	Any
Tags:	Write Protected Memory

Description:
In SQL Editor, when editing table data and deleting more than 200 rows a Critical Error occurs - 

"Attempting to Read or Write protected memory. This is often an indication that other memory is corrupt"

Pressing the delete button shows the right slider moving through the records, then suddenly, before finishing the error occurs.

This is before selecting Commit.

How to repeat:
It is a simple integer column, numbered with values 1 to 256 Default INNODB table. The error occurs either by selecting the top left cell (all) or by dragging the cursor and marking the rows. 

Error only occurs in the Bottom Panel - Either the Delete Keyboard button or Mouse Right Click - Delete.

Deleting from external attached tables or from the SQL Statement Window "DELETE FROM ..", functions correctly.

Suggested fix:
Possibly memory buffering error whilst storing for commit, since the other methods are direct.

May also be the 'lower panel display' trying to show the annimated deletion.

Write Protected Memory Error Message

Attachment: WPE.PNG (image/x-png, text), 28.81 KiB.

Thank you for the bug report. Verified on Vista X86_64.

Same bug on windows XP SP3 with:
- "Edit Table Data"
- CTRL-A + right click "Delete row(s)"

It's OK for exactly 200 rows.

fix confirmed in repository

An entry has been added to the 5.2.20 changelog:

In the results editor of the SQL Editor, deleting more than two hundred records resulted in the following error:

Attempting to Read or Write protected memory. This is often an indication that other
memory is corrupt

This happened when using either the delete key or the Delete Rows context-sensitive menu option.