MySQL Bugs: #67870: System Reports out of Memory exception - Workstation with 24GB of RAM, thread us

Bug #67870	System Reports out of Memory exception - Workstation with 24GB of RAM, thread us
Submitted:	10 Dec 2012 23:03	Modified:	8 Feb 2014 1:06
Reporter:	Christopher Hall	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	5.2.44	OS:	Windows (Microsoft (build 9200), 64-bit)
Assigned to:		CPU Architecture:	Any
Tags:	WBBugReporter

Description:
Working with a fairly complex model (I will be happy to share it if this will be helpful in testing. After several hours of working with it, MySQL Workbench will crash with an out of Memory Exception. The changes at this point are all rearranging items on the Diagram View.

----- Developer Notes -----

MySQL Workbench CE for Windows version 5.2.44  revision 9933; Win8 Pro, 24GB RAM, 19.2GB Available at time of crash.
Configuration Directory: C:\Users\Chris\AppData\Roaming\MySQL\Workbench
Data Directory: C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE
Cairo Version: 1.8.8
OS: Microsoft  (build 9200), 64-bit
CPU: 8x Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz, 24.0 GiB RAM
Current user language: English (United States)

Exception = System.OutOfMemoryException
Message = Exception of type 'System.OutOfMemoryException' was thrown.
FullText = System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
   at MySQL.GUI.Workbench.Program.HandleException(Object o)
   at MySQL.GUI.Workbench.Program.OnGuiUnhandledException(Object sender, ThreadExceptionEventArgs e)
   at System.Windows.Forms.Application.ThreadContext.OnThreadException(Exception t)
   at System.Windows.Forms.Control.WndProcException(Exception e)
   at System.Windows.Forms.Control.ControlNativeWindow.OnThreadException(Exception e)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.Run(ApplicationContext context)
   at MySQL.GUI.Workbench.Program.Main(String[] Args)

How to repeat:
I haven't isolated any particular action that causes the crash, I'm hoping that the log might help, or that the size of the file might play into this. (Note: I was unable to sign up for a mysql.com account using the "Sign Up" button on this form, the system claimed that there was insufficient memory available. I was able to launch a browser with no issues and sign up that way; however, so the issue appears to be internal to MySQL Workbench, not the OS.

Thank you for the bug report. Please provide the model file (private if you wish). Thanks.

WB is (in)famous for its leaks.

Here is another one:
http://bugs.mysql.com/bug.php?id=58405
(not fixed after 2 years!)

Peter
(not a mySQL/Oracle person)

Magento 1.7.02 Revision Database Schema

Attachment: Magento 1702.mwb (application/octet-stream, text), 467.40 KiB.

Thank you for the feedback. Indeed just moving tables objects in the diagram is noticeable with the task manager the memory increasing.

Posted by developer:
 
Verified.

This bug is fixed, and the changelog was merged with a similar bug (MySQL Bug #58405) that was closed in 6.1.1. Here's its changelog entry:

        On Microsoft Windows, opening and closing models/diagrams would
        increase the number of open GDI (Graphics Device Interface)
        objects as they were kept in memory for the undo queue. The
        required memory for this task was decreased.

Thank you for the bug report.