Bug #53491 Attempted to read or write protected memory
Submitted: 7 May 2010 13:43 Modified: 25 Jun 2010 13:25
Reporter: Scott Noyes Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:5.2.20 OS:Windows (XP)
Assigned to: CPU Architecture:Any

[7 May 2010 13:43] Scott Noyes 
Description:
MySQL Workbench has encountered a problem

Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

How to repeat:
Fresh install of 5.2.20

<Server Administration> New Server Instance
Remote Host
enter host name (to which I happen also to be connected with Putty)
Next
change port from 3306 to 5146
Next
error box pops up

See screen recording at http://www.screentoaster.com/watch/stWU9dRkBIR15cQl5VXl5dVFJR/workbench_error
[7 May 2010 14:00] MySQL Verification Team 
- Error persists after a reboot
- Error persists if I leave the default port 3306
- Same message box if I switch to TCP/IP over SSH and enter the SSH password under "Store In Vault..."
[17 May 2010 17:37] Johannes Taxacher 
Hi Scott,

could you try with latest version if the problem still exists?
thanks in advance
[18 May 2010 4:07] MySQL Verification Team 
Problem persists in 5.2.21 RC.
[17 Jun 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".
[25 Jun 2010 13:25] MySQL Verification Team 
Seems to work properly in 5.2.24. My first attempt to open a saved connection indicated something like "could not decrypt password vault", but clearing the password and entering it again solved that. Since the original error appeared whenever dealing with the password vault, I suspect there was some kind of corruption there all along.