Bug #37178 DBDesigner4 model import error
Submitted: 4 Jun 2008 0:56 Modified: 11 Nov 2008 10:27
Reporter: Rodrigo Ribeiro Email Updates:
Status: Closed Impact on me:
Category:MySQL Workbench Severity:S1 (Critical)
Version:5.0.22 OS:Microsoft Windows (2003 Server)
Assigned to: CPU Architecture:Any
Tags: Cairo, DBdesigner, import
Triage: D2 (Serious)

[4 Jun 2008 0:56] Rodrigo Ribeiro
When importing a DBDesigner model (333 tables, InnoDB) the RAM usage goes up to near 1GB.
The Designer crashes giving a internal (not S.O.) message, probably about rendering issues. These message appears to be handled exception about "cairo" context creation.

I could save de model but when I try to open it the rendering eat the RAM up to 500MB and freeze Workbench.

How to repeat:
Try to import a big model from DBDesigner4 in Windows (XP, Vista or 2003 gives the same bug)

Suggested fix:
Do not use so much memory to render things
[4 Jun 2008 12:52] Rodrigo Ribeiro
Correction: where you see GB should me MB and where you see MB should be KB
[4 Jun 2008 12:54] Rodrigo Ribeiro
The exact Error Message is "Error creating cairo context: out of memory"
[4 Jun 2008 12:56] Rodrigo Ribeiro
The exact Error Message is "Error creating cairo context: out of memory"
[4 Jun 2008 17:30] Miguel Solorzano
Error message

Attachment: memory_error.png (image/png, text), 28.49 KiB.

[4 Jun 2008 17:31] Miguel Solorzano
Thank you for the bug report.
[9 Jun 2008 17:00] Randy Larson
I have the same problem rendering a 200+ table database. I seems to be the diagram engine that is having the issue. I can import SQL code into Workbench, but as soon as I tell it to create diagram from catalog objects it has the same memory issue. Also import from DBDesigner file also runs into the same issue. I have XP Professional with 1.5GB Ram.
[11 Jun 2008 15:14] Csaba Karoly
I also have a large DBDesigner model with 237 tables and 800+ relations.
I have seen the cairo message but I have seen other messages too:
"Unknown Exception caught in c:\documents and settings\mysqldev\my documents\visual studio 2005\projects\workbench\backend\windows\wb.wr\src\Wb.h at line 1010."
After this I got the diagram with some tables. I clicked on a table and I got the next message:
"Unhandled exception has occured in your application. If you click Continue the application will ignore this error and attempt to continue. If you click Quit the app will close immediately.
Collection was modified; enumeration operation may not execute."
[11 Jun 2008 15:16] Csaba Karoly
Sorry! I have Vista Business with 2 GB RAM.
[27 Jun 2008 17:41] Sean Dotson
I have this error come up when importing and creating the model.
[4 Aug 2008 10:27] Mike Lischke
Fix deferred to version 5.1 due to required changes needed to make the fix even possible. There is a new bug report reflecting this: bug #38536
[29 Oct 2008 16:23] Johannes Taxacher
Alfredo found the source of the excessive memory usage in improper caching of canvas figures. this is fixed now and the memory usage of WB now stays beneath 100MB most of the time even for very large models.
this fix will be in 5.0.27
[11 Nov 2008 10:27] Tony Bedford
An entry has been added to the 5.0.27 changelog:

When a DBDesigner model with 333 tables was imported into Workbench the RAM usage went up to approximately 1GB. Workbench then crashed with the following exception: 

  Error creating cairo context: out of memory