MySQL Bugs: #60662: MySQL Workbench Crashing Often

Bug #60662	MySQL Workbench Crashing Often
Submitted:	26 Mar 2011 20:29	Modified:	9 May 2011 18:16
Reporter:	Bill T. Jurczyn	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S2 (Serious)
Version:	5.2.31 CE	OS:	Windows (Windows 7 64-bit)
Assigned to:		CPU Architecture:	Any

Description:
MySQL Workbench reports "not enough storage is available to process this command" when constructing EER diagrams of any substantial size or when trying to process SQL load files with a substantial amount of INSERT statements. This occurs despite having 8GB of memory on my machine (with typical 4-5 GB free when these errors occur) and 2 TB of hard drive storage of which 12 GB is given to the paging file.

These errors screens cannot be dismissed and I'm compelled to exit the program and open it again, where I attempt to complete the task until these errors occur. Often, I give up on the product entirely because it doesn't seem capable of performing this simple, common, and customary tasks for db management apps.

How to repeat:
Simply try performing any task of substantial size and the application will fail.

Please, send the output of Help > System Info menu item.

MySQL Workbench CE for Windows version 5.2.31

Configuration Directory: C:\Users\Computer\AppData\Roaming\MySQL\Workbench

Data Directory: C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE

Cairo Version: 1.8.8

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

OpenGL Driver Version: 4.0.10207 Compatibility Profile Context

OS: Microsoft Windows 7  (build 7600), 64-bit

CPU: 8x Intel(R) Core(TM) i7 CPU         930  @ 2.80GHz, 8.0 GiB RAM

Active video adapter: ATI Radeon HD 5770

Installed video RAM: 1024 MB

Current video mode: 1920 x 1200 x 4294967296 colors

Used bit depth: 32

Driver version: 8.773.0.0

Installed display drivers: aticfx64.dll,aticfx64.dll,aticfx64.dll,aticfx32,aticfx32,aticfx32,atiumd64.dll,atidxx64.dll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll

Current user language: English (United States)

How large are those SQL files that you can NOT process successfully?

The size of the individual SQL files that fail are in the 410+ MB range. They will consistently fail if I attempt to process them via the "SQL Development" interface of the MySQL Workbench. (open a sql script file) The CLI of MySQL also fails to process these files -- without any feedback (success or fail). I've determined that the CLI consistently fails because only a fraction of the files are loaded before the CLI terminates.

However, the "Data Dump" import from disk feature of the "Server Administration" interface provided limited success if one selects "Import From Self-Contained File". The processing time is unreasonably excessive. If one choses "Import From Dump Project Folder" the load will fail when attempting to import the entire schema. (The feedback is written to the "log" field on that particular screen, and the application just sits there doing nothing.)

Additionally, I have client SQL files in the 1.5MB range that contain over a hundred table definitions (150) with some sample data (a few dozen records per table). This loads without problem (via CLI or Data Dump import feature); however, "Data Modeling" feature of MySQL Workbench will fail if one tries to create an EER Model from the imported schema. You can choose the database to work with and it will perform the initial steps of importing the schema (all 150 tables); however, when you attempt to construct EER diagrams by reverse engineering the database -- the initial diagrams will be created -- but the moment you open the diagrams and start working with them MySQL Workbench locks up with constant error messages that cannot be dismissed (see original input) and one has to forcefully terminate the program from the task bar or task manager.

Thank you for the feedback. Are you tried 5.2.33 version?. Thanks.

Downloaded and installed MySQL Workbench 5.2.33 Win-32 today. Will work with product to see if problems reported in version 5.2.31 are resolved. First impression -- new version loads a lot slower and the reorganization of the interface is more difficult to see because of font and color selections and some items do not repond to mouse-over actions when they should.

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

Backup and recovery feature of Workbench v.5.2.33 rev.7508 installed to resolved problems with Workbench 5.2.31. has worked-out. The update data export and restore feature functions without the application failing.

The Data Modeling feature is now capable of reverse engineering databases of modest size (a couple dozen objects) and creating diagrams that are both workable and do not crash the system. I haven't tested this feature on databases containing over a 150 objects (as was the case when this feature crashed in version 5.2.31).

Feature problems resolved with application update.