Bug #40762 Memory error freezes/crashes computer when selecting multiple tables.
Submitted: 15 Nov 2008 20:49 Modified: 8 Jul 2009 7:42
Reporter: Witek Radomski Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S1 (Critical)
Version:5.0.29 OS:Windows (XP)
Assigned to: Assigned Account CPU Architecture:Any

[15 Nov 2008 20:49] Witek Radomski
Description:
Occasionally, when selecting multiple tables with the mouse in the Diagram view, MySQL Workbench has a serious crash, creating infinite numbers of error windows saying "Attempted to read or write protected memory. This is often an indication that other memory is corrupt." Right before this happens, another error appears in MySQL workbench, but I have not been able to get a clear viewof that error.

After a few moments, the entire computer freezes, including the mouse cursor, and a cold system reboot is required.

How to repeat:
I've had this happen about 4-5 times now, but I can't find a simple step-by-step way to reproduce it. As it just happened this morning, here's what I did:

Opened MySQL Workbench and loaded a mwb file, which opened the Diagram view.
Saved the mwb file as a new file.
Minimized MySQL Workbench and did a bit of web browsing.
Maximized MySQL Workbench and dragged a selection box around 3 tables (these tables did not have foreign keys, just free-floating tables).

First error popped up. I hit OK (don't remember if that was the button label ..).

Infinite memory errors start appearing up in a loop, filling my screen, and causing the Windows error sound to go "ding, ding, ding, ding, ding ..." endlessly.

I opened Windows Task Manager by pressing Ctrl-Alt-Delete but as this opened, the mouse froze and computer stayed fully frozen, while the error sound kept beeping for about 5 minutes while I took a picture of the screen with my digital camera and then rebooted the computer.
[16 Nov 2008 11:30] Valeriy Kravchuk
Thank you for a problem report. Please, upload smallest problematic .mwb file and exact steps on how to repeat the problem with it. Do you have XP SP2 or SP3, 32-bit or 64-bit?
[20 Nov 2008 9:00] tomas korc
I also encounter infinite number of error windows saying "Attempted to read or write protected memory... when working with some of my schemas in WB 5.0.27 on 32bit XP SP2.

How to repeat:
When clicking on table Privilege I get windows saying "Attempted to read or write protected memory...

When clicking on table Group I get Microsoft.Net Framework window with unhandled exception message plus these repeating windows "Attempted to read or write protected memory... and there are red crosses in Catalog and small canvas windows to the right.

I send you the db file.
Thank you
[20 Nov 2008 9:04] tomas korc
db file for Bug #40762 by Tomas Korc

Attachment: db for Bug #40762 by Korc.mwb (application/octet-stream, text), 10.54 KiB.

[20 Nov 2008 9:19] tomas korc
.. to the same schema, when I remove the menu_cs table, both problems, descibed above, disappear.
[20 Nov 2008 22:00] Witek Radomski
Hello,
I am on Windows XP SP3, 32bit.

The errors seem to happen when:
Selecting a group of tables in Diagram View.
Creating a new table in Diagram View.

The errors usually happen after loading a .mwb file or period of inactivity.

I found a way to avoid the error, is to simply click once on any 1 table to select it, and then click away to deselect. After doing that, I can select multiple tables or create new tables without the error happening.
[24 Nov 2008 19:43] Witek Radomski
Tomas Korc's db produced the same problem for me as I've been having.

In my own schemas, I've found that the error also occurs after loading a mwb file with 41 tables, then clicking on a table in the Diagram view, then clicking on an empty area to deselect it. Error message pops up and same issue happens.

I've been able to work around it by closing Diagram view, opening editor for a few tables, opening Diagram view, double clicking carefully on a few tables, and then usually the problem goes away for that session and I can work without problems.

But once I close MySQL Workbench and load the same mwb file again, the problem reoccurs.
[26 Nov 2008 13:43] Susanne Ebrecht
Many thanks for writing a bug report. I can't repeat this behaviour. Also not with idling more then 8 hours.

I would assume this is a memory problem. How many RAM has your machine?
[1 Dec 2008 5:22] Witek Radomski
Hello,

I have 4 gb ram in my machine. Tomas Korc's mwb file consistently produces the crash for me.. strange that it isn't doing the same to some other people. I'm running MySQL Workbench 5.0.27 SE. Bug happens so often (few times a day) that it makes it difficult to work.
[2 Dec 2008 6:48] Witek Radomski
A little more information about my setup.. in case this has any use.

I'm running dual monitors with UltraMon, 1900x1200 and 1600x1200. I run MySQL Workbench on the 1900x1200 widescreen monitor.

I wonder if other people having this bug are also on dual monitor and/or high-res screens?
[4 Dec 2008 13:08] MySQL Verification Team
I could not repeat this issue on my XP SP3 box:

Looking for user plugins in C:\Documents and Settings\miguel\Dados de aplicativos\MySQL\Workbench\modules
Looking for user plugins in C:\Documents and Settings\miguel\Dados de aplicativos\MySQL\Workbench\plugins
MySQL Workbench SE for Windows version 5.0.27
Cairo Version: 1.5.12
Rendering Mode: GDI Rendering
OpenGL Driver Version: Not Detected
OS: Windows XP
CPU: Intel(R) Celeron(R) M CPU        420  @ 1.60GHz, 0.9 GB RAM
Video adapter info:
Adapter type: ATI RADEON XPRESS 200M Series
Chip Type: ATI display adapter (0x5A62)
BIOS String: BK-ATI VER008.050I.026.000
Video Memory: 65536 KB
[4 Dec 2008 17:52] tomas korc
Hello,

as for the RAM, I encountered the problem on my notebook with 1,5 GB and also on PC with 448 MB at time of my first reporting. 

Somehow, this error happens less frequently in recent days and what is strange, I cannot repeat the error with the submitted file right now.

I also use dual monitor configuration, both with 1024x768.
[15 Dec 2008 13:40] Susanne Ebrecht
Many thanks for writing a bug report.

Unfortunately, nobody of us is able to repeat this.

Please try newer version: Workbench 5.0.29 and let us know if you still have this problem.
[15 Dec 2008 21:49] Witek Radomski
Hello,

Yes, I'm still having this problem in 5.0.29. I will try to do some more extensive testing myself and write the step-by-step method and/or files that produce this bug.
[16 Dec 2008 13:55] Susanne Ebrecht
I can reproduce this with Workbench 5.0.29 OSS.

I took given from tomas mwb file.

I opened it by just clicking on it.

Not starting Workbench before, just let Workbench start by clicking on the file.

I selected a few tables and got the German Windows Error message:

"Es wurde versucht, im geschützten Speicher zu lesen oder zu schreiben. Dies ist häufig ein Hinweis darauf, dass anderer Speicher beschädigt ist."

The English translation should be:
"Attempted to read or write protected memory. This is often an indication that other memory is corrupt"
[16 Dec 2008 14:24] Susanne Ebrecht
I just made a HDD clean up and a disk check. For disk check I needed to reboot so that disk check was executed. After that I couldn't reproduce this error anymore.

Please try this too and let us know if that helped.

It really seems it is more Windows related then Workbench related.
[17 Jan 2009 0: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".
[28 Jan 2009 15:09] martin weber
error coming always up when trying to edit a table , error newly in  v5.0.29!!!!!
[1 Jun 2009 14:25] Lenny schreib
Same problem to me - can reproduce it with this:

 - Double Click my.mwb
 - MySQL Workbench opens - everything is fine
 - right click on a table -> EDIT...
 - ERROR

Workaround for me:

 - Double Click my.mwb
 - MySQL Workbench opens - everything is fine
 - left click on the table
 - waiting a few seconds
 - right click on a table -> EDIT...
 - no error, ready to edit

And the error is coming up while doing other things with the workbench - but cannot reproduce them. I think I'm to fast with doing things.

System:
Dual Core 2*2,4GHZ
2GB RAM dual channel
ATI x1950pro
MySQL Workbench 5.0.30 OSS
[1 Jun 2009 14:34] Alfredo Kojima
Hi

If possible, please check if this bug is still present in 5.1 BETA for Windows.
[8 Jun 2009 7:42] Mike Lischke
Please check with version 5.1 of Workbench. We are focussing on WB 5.1 and would like to fix this problem there if it still exists, rather than WB 5.0. Thank you.
[8 Jul 2009 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".