MySQL Bugs: #42460: System.AccessViolationException: Attempted to read or write protected memory.

Bug #42460	System.AccessViolationException: Attempted to read or write protected memory.
Submitted:	29 Jan 2009 16:54	Modified:	4 Mar 2009 9:41
Reporter:	Marco Gracio	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	5.0.29	OS:	Windows (XP SP)
Assigned to:		CPU Architecture:	Any
Tags:	bug, Critical

Description:
Hi.
I have been getting this error frequently ever since version 5.027, or since my database file has grow larger, I am not sure.
It is rather random so I do not know exactly which operation triggers it, but it seems to occur when trying to edit a table, it also happened while trying to create a new relationship between 2 tables. I will upload 2 files, one with the error details other with the database file.

How to repeat:
It is rather random so I do not know exactly which operation triggers it, but it seems to occur when trying to edit a table, it also happened while trying to create a new relationship between 2 tables. Sometimes just hovering the mouse over a relationship makes it happen

Error details file

Attachment: erro mysql workbench.rtf (application/msword, text), 6.28 KiB.

Thank you for the bug report. Do you have checked the option Automatically Reopen Last Opened Model When Started....?. Thanks in advance.

Hi!
I had it enabled at one time, which sometimes caused the program to continually crash on startup upon loading the workbench file and when the problem manifested itself. So as soon I could, I disabled it.
Thanks for your support!

Hello Marco,

unfortunately, you are not the only one with this problem. We already tried a lot to reproduce this issue. Non of our employees ever could reproduce it.

We are pretty sure there is a problem but we are fishing in the dark.

I once could reproduce it but I cleaned/checked my disc after it and cleaning/checking disc helped to let the problem go away ....

This could be related to bug #42435

It also could be related to hardware requirements ....

Anyway, please observe this more longer and let us know if you will figure out some more details.

Also you have a bigger chance that this will be gone away with next upcoming version.

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