MySQL Bugs: #54513: Attempted to read or write protected memory

Bug #54513	Attempted to read or write protected memory
Submitted:	15 Jun 2010 13:19	Modified:	16 Jun 2010 16:51
Reporter:	Keith Bergum	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	5.2.22	OS:	Windows
Assigned to:		CPU Architecture:	Any

Description:
I open up the MySQL Workbench.
Opens just fine.
Any attempt to Open Connection to Start Querying, Any attempt to Manage Server Instances basically any attempt to click on anything and do anything gets me the error 

MySQL Workbench has encountered a problem.

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

We are sorry for the inconvenience but an unexpected exception has been raised by one of the MySQL Workbench modules. In order to fix this issue we would kindly ask you to file a bug report. You can do that by pressing the [Report Bug] button below. 

Please make sure to include a detailed description of your actions that lead to this problem.

Thanks a lot for taking the time to help us improve MySQL Workbench!

The MySQL Workbench Team

Actually started on very 5.1.16 where I decided to upgrade to this version but problem is still there.

How to repeat:
Very easy to do. Just attempt to do anything. Can be repeated on everything I do.

Thank you for the problem report. Please, send the results from Help > System Info menu item.

What exact version(s) of MySQL server, x.y.z, local or remote, you are trying to work with?

I work currently with three different MySql databases

Distribution 5.0.77 

Distribution 5.0.15-nt

Distribution 5.0.21-max-log

MySQL Workbench OSS for Windows version 5.2.22

Cairo Version: 1.8.8

Rendering Mode: OpenGL is available on this system, so OpenGL is used for rendering.

OpenGL Driver Version: 2.0.3

OS: Microsoft Windows XP Professional Service Pack 3 (build 2600)

CPU: 2x Intel(R) Xeon(R) CPU            5160  @ 3.00GHz, 3.0 GiB RAM

Video adapter info:

Adapter type: NVIDIA Quadro FX 1500

Chip Type: Quadro FX 1500

BIOS String: Version 5.71.22.31.07

Video Memory: 262144 KB

I couldn't repeat on Vista Home Premium 64-bit.

Duplicated under the following:

MySQL Workbench OSS for Windows version 5.2.22
Cairo Version: 1.8.8
Rendering Mode: OpenGL is available on this system, so OpenGL is used for rendering.
OpenGL Driver Version: 2.1.2
OS: Microsoft Windows 7 Ultimate Edition (build 7600), 64-bit
CPU: 2x Intel(R) Core(TM)2 CPU          6600  @ 2.40GHz, 4.0 GiB RAM
Video adapter info:
Adapter type: NVIDIA GeForce 7600 GT 
Chip Type: GeForce 7600 GT
BIOS String: Version 5.73.22.51.1
Video Memory: 262144 KB

More detailed steps to duplicate:

* Double-click on existing db connection (created in previous Workbench version)

* Create a new connection and store a password in the vault or click 'Test Connection'

The severity of this should be upgraded to Critical.  Workbench is useless w/out being able to connect to the DB.

Let me know if you need any more info to troubleshoot this one.

Same problem under 5.2.21.

I have the same problem with Workbench v5.2.22 as of today.   No idea what changed or what may have caused this.  The only thing i did today unusual was change my passwords for Admin and myself (also Admin) on my machine.   And i may have stopped a few unecessary services running on my Win XP Pro OS.

This is horrible.  

Error :    MySQL has encountered a problem

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

Duplicate of Bug #53704

Confirmed solution from #53704.

More specifically, deleting or renaming the following file and restarting Workbench solves the issue:

"%APPDATA%[\Roaming]\MySQL\Workbench\workbench_user_data.dat"

However, since this issue has been present for some time, and is still cropping up in 5.2.22, should it really be closed?

In my case, the issue was apparently caused when moving from XP-32 to Win7-64, but with the same Workbench version.  If there's some back-end identity or key differences, I can understand the old vault not working, but Workbench should be able to gracefully handle that.

It is a nice solution to delete the file however

"%APPDATA%[\Roaming]\MySQL\Workbench\workbench_user_data.dat"

however I have done a complete search of my system and there is no file on my system with that name.

Found it, after looking at the other incident, I did find the valut and by deleting that file and reentering all your passwords everything works.

Thanks.

On Windows 7 Ultimate, I am running version 5.2.26 of Workbench.  I could not find the file either, but found something in the other report that I could delete the MySQL folder from the user profile directories AppData\Roaming\ directory.  I did this and restarted the Workbench, but still have the same problem.

Windows 7 64bit
Workbench 5.2.29 CE rev-6756

Deleted workbench_user_data.dat
> del %APPDATA%\MySQL\Workbench\workbench_user_data.dat

On the model that was not working I did a Forward Engineer to the point where it shows you the SQL script to be executed. I saved the script to a file and stopped the Forward Engineering at that point.

Next I created a new model from the .sql script I saved. Once that is loaded I deleted the model not working. Restarted workbench and now it seems to be working for me.

A side note and I am not sure if this related or not but... this started happening after I played around with system paging file. It is now set to let the system manage it.