Bug #51714 OutOfMemory error
Submitted: 4 Mar 2010 11:02 Modified: 9 Jan 2015 16:02
Reporter: Thomas Manson Email Updates:
Status: Can't repeat Impact on me:
Category:MySQL Workbench: Modeling Severity:S2 (Serious)
Version:5.2.15 Revision 5053, 5.2.16 OS:Any (XP SP3, Ubuntu)
Assigned to: Assigned Account CPU Architecture:Any
Tags: crash, Out Of Memory error

[4 Mar 2010 11:02] Thomas Manson
MySQL Workbench was left open for a long time without any activity on it for at least 2 days, when I get back on my computer I see the Out Of Memory error.

I had a model open with 91 tables with relationship between table (innodb engine)

How to repeat:
maybe letting open like i said
[4 Mar 2010 12:48] Thomas Manson

 Issue as been reproduced. I'll attached the model I'm using.

 Here is the crash info : 

Exception = System.OutOfMemoryException
Message = Une exception de type 'System.OutOfMemoryException' a été levée.
FullText = System.OutOfMemoryException: Une exception de type 'System.OutOfMemoryException' a été levée.
   à System.String.Concat(String str0, String str1)
   à MySQL.GUI.Workbench.WorkbenchOutputForm.PrintOutputText(String OutputText)
   à MySQL.GUI.Workbench.MainForm.PrintOutputText(String OutputText)
   à MySQL.Workbench.WbFrontendCallbacks.print_output_wrapper(basic_string<char\,std::char_traits<char>\,std::allocator<char> >* str1)
   à sigc.pointer_functor1<std::basic_string<char,std::char_traits<char>,std::allocator<char> > const &,void>.()(pointer_functor1<std::basic_string<char\,std::char_traits<char>\,std::allocator<char> > const \&\,void>* , basic_string<char\,std::char_traits<char>\,std::allocator<char> >* _A_a1)
   à sigc.adaptor_functor<sigc::pointer_functor1<std::basic_string<char,std::char_traits<char>,std::allocator<char> > const &,void> >.operator()<class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &>(adaptor_functor<sigc::pointer_functor1<std::basic_string<char\,std::char_traits<char>\,std::allocator<char> > const \&\,void> >* , basic_string<char\,std::char_traits<char>\,std::allocator<char> >* _A_arg1)
   à sigc.internal.slot_call1<sigc::pointer_functor1<std::basic_string<char,std::char_traits<char>,std::allocator<char> > const &,void>,void,std::basic_string<char,std::char_traits<char>,std::allocator<char> > >.call_it(slot_rep* rep, basic_string<char\,std::char_traits<char>\,std::allocator<char> >* a_1)
[4 Mar 2010 12:50] Thomas Manson
Note that I've left open the workbench for one or two hours.
[10 Mar 2010 10:37] Susanne Ebrecht
Do you have memory problems too when you don't use Workbench but your computer is idling 2 days?
[10 Mar 2010 10:45] Thomas Manson
Hi Susanne,

 I've no memory issue on my computer. I've 4GB of memory (C2D 7250 processor). I often have several big application open (up to 4 eclipse instance with tomcat and jboss running, TOAD, Firefox, word, excel, Terminal Server, TIBCO products), but I've no speed issue, I can still run more app without any problem. Sometime firefox eat up to 1.2GB of memory and use a lot of cpu when it happen, but it was not the case when mysql workbench crashes. 

When MySQL Workbench crashes, I didn't experiences any other memory issue.
I'm currently out of the office, but next time I'll try to reproduce the issue and check the memory footprint of mysql workbench.

[11 Mar 2010 6:59] Susanne Ebrecht
Verified as described.

1) Open workbench
2) Load mwb file
3) Create diagram
4) wait ....

In my test after 36 hours ...

5) click onto a table

Result:  crash
[11 Mar 2010 7:01] Susanne Ebrecht
Additionally, I have to say here that I shrunk down the window and did my usual work further on on my computer (besides during night of course).
[5 May 2010 12:14] Alfredo Kojima
Added bug #53401 as duplicate
[27 Jul 2010 16:08] Alfredo Kojima
Looking at the stack trace, it seems it was in the process of printing something to the output window.
Do you see something getting periodically printed to the Output tab when running WB for long times, esp
without any direct interaction from you?