MySQL Bugs: #59680: attempted to read or write protected memory, suggests corruption

Bug #59680	attempted to read or write protected memory, suggests corruption
Submitted:	23 Jan 2011 16:48	Modified:	29 May 2011 17:59
Reporter:	Judy Whiteside	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S3 (Non-critical)
Version:	5.2.31 CE	OS:	Windows (Win 7 Pro x64)
Assigned to:		CPU Architecture:	Any
Tags:	Memory

Description:
I was copying a production database into my development environment.
I had just done:
drop schema / create schema / run .sql code created by phpmyadmin EXPORT for the entire db (17 tables, none huge) / refresh all / open existing .sql script / open existing 2nd .sql script 

Then message pops up - Workbench has encountered a problem. The message requested that I file a bug report.

The EXPORT .sql file was 3112 lines long

After this when I right-clicked a table to show rows, the memory-execption problem found popup shows again.

I had run other work with workbench in this session just fine.
I have done this process before with no problem.
I will clean out this schema and try the process again.
(This was a 2nd copy of my db so I'm not stuck.)

How to repeat:
drop schema
create schema
run .sql code created by phpmyadmin EXPORT for the entire db (17 tables, none huge)
refresh all
open existing .sql script
open existing 2nd .sql script 

I don't think opening the existing .sql script is relevant (very small, and I had not run them.)

When I closed workbench and reopened it, everything seems to work fine.
I did NOT have to purge that schema and re-create it.

I am able to see the tables and to retrieve records and to run scripts.
It healed itself.

fyi. at the time of the error, I had VS2005 loaded and MS Outlook. 
Also Mcaffee and firefox running. Otherwise pretty regular system stuff.

Please, send the output of Help > System Info menu item.

Output from Workbench Help > System info:

MySQL Workbench CE for Windows version 5.2.31
Configuration Directory: C:\Users\Judy\AppData\Roaming\MySQL\Workbench
Data Directory: C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE
Cairo Version: 1.8.8
Rendering Mode: OpenGL is available on this system, so OpenGL is used for rendering.
OpenGL Driver Version: 3.2.0
OS: Microsoft Windows 7  (build 7600), 64-bit
CPU: 8x Intel(R) Core(TM) i7 CPU         860  @ 2.80GHz, 8.0 GiB RAM
Active video adapter: NVIDIA GeForce GTS 240
Installed video RAM: 1024 MB
Current video mode: 1920 x 1080 x 4294967296 colors
Used bit depth: 32
Driver version: 8.16.11.9107
Installed display drivers: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Current user language: English (United States)

When you'll get similar error again, please, right click somewhere in the error dialog box with no text and use Copy stack trace to clipboard context menu item. Send stack trace to this report.

see the attached file with the stack trace. also another memory-related-error occurred and I got a slightly different error box. I have included the DETAILS from that box in the file.

When I got the error I was editing a stored routine. I had just hit APPLY and it worked ok (i have verified the changes) and then I hit CLOSE and the error occurred.

stack trace and DETAILS of memory error event

Attachment: workbench memory violation.txt (text/plain), 1.29 KiB.

DETAILS from a memory exception error event

Attachment: workbench memory violation2.txt (text/plain), 7.83 KiB.

Could you please provide the *.sql file. Thanks in advance.

sql file for demonstration

Attachment: wcarc_vault.sql (text/x-sql), 136.41 KiB.

This file attached wcarc_vault.sql is probably not the exact file in question, but is very, very similar to the one I was using when the problem occurred.

Since this original error, I have seen a memory-relevant exception error 3 or 4 times. I saw one again yesterday and submitted another report (bug report #60194). I think they must be similar. When they occur I am working in Workbench, in the sql editor, and clicking on the toolbar (most likely Open, Save, Execute) and in the object browser panel (probably opening up + sign, or selecting rows or alter routine). I do not see any consistent pattern of an exact sequence that causes the problem. 

If it happens again, what kind of information should I collect to report?
I will note the exact sql file involved (if any) and the toolbar action items, etc. Would a capture of the system services be useful? What else?

Hi Judy,

in any case, the stacktrace is the most important part of information (the one gathered from right-click into the bug-window), along with a description of your actions up to the point of the error (as precise as possible).
thanks for your help!

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".