MySQL Bugs: #53704: Attempted to read/write protected memory

Bug #53704	Attempted to read/write protected memory
Submitted:	17 May 2010 14:13	Modified:	12 Jun 2010 9:59
Reporter:	Carlos Ravelo	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S3 (Non-critical)
Version:	5.2.21 OSS	OS:	Windows (XP Pro SP3)
Assigned to:	Mike Lischke	CPU Architecture:	Any

Description:
When double click on a connection on the home screen to go to the SQL Editor an error message comes up with the following message:

Attempted to read/write protected memory. This is often and indication that other memory is corrupt.

Same thing happens if you double click on a server instance for server administration.

The old mysql essentials tools work, the server is working fine, I can administer it with phpMyAdmin and my php applications work.

I tried uninstalling workbench, restarting and reinstalling it. I tried copying libmysql from the server to workbench and to the system32 folder. 

This problem has been going one since 5.2.14 beta or earlier I cant pinpoint exactly when did it start.

How to repeat:
Create a new conection or server instance in workbench and then try to access the SQL editor or the server administration.

It also happens when trying to synchronize or forward engineer a model, at the point when Workbench has to connect to the server.

I have pinpointed the source of the error. Is the password vault. The error comes up when you try to clear the vault or store a password in the vault. the other errors come up when Workbench is trying to access the vault to make the connection.

The problem was solved by deleting this folder and reopening Workbench

C:\Documents and Settings\[username]\Application Data\MySQL

I am guessing that the Password vault is kept there.

Thank you for the bug report. Actually repeatable with the password vault issue.

I could not repeat this problem at all, neither on XP nor Win7, but I took measures to make the whole process more stable. The new code will available with the next release. Please test it again when that is available and let us know the outcome.

It happened because I had installed earlier versions of the workbench, beta and had saved a password to the vault. When I uninstalled workbench to install the newer versions the uninstall didn't delete the old vault. The new version was crashing because of it.

I haven't had a problem anymore with the new versions so I think this can be closed, I think it was just because of changes to the way the password is saved in the vault.

thank you

I forgot to say that yes I will test the new code and report.

thank you!

I am having this same issue on Windows 7 Ultimate with Workbench 5.2.26.  I have tried deleting the MySQL folder from c:\users\[my_profile]\AppData\Roaming\ and then re-opening MySQL Workbench, but I still get the exact same error message.  Any more suggestions?