Bug #66089 Error in workbech migrate
Submitted: 30 Jul 2012 16:24 Modified: 1 Sep 2012 20:13
Reporter: Tony Medici Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench: Migration Severity:S1 (Critical)
Version:5.2.41 OS:Microsoft Windows (Microsoft Windows Server 2008 R2 Standard Edition Service Pack 1 (build 7601), 64-bit)
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[30 Jul 2012 16:24] Tony Medici
Description:
When trying to migrate a SQL Server 2008 R2 database, the app crashes about two thirds of the way at the "Migration" stage before the SQL Create statements are produced

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

MySQL Workbench CE for Windows version 5.2.41  revision 9724
Configuration Directory: C:\Users\Tony.Medici\AppData\Roaming\MySQL\Workbench
Data Directory: C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE
Cairo Version: 1.8.8
OS: Microsoft Windows Server 2008 R2 Standard Edition Service Pack 1 (build 7601), 64-bit
CPU: 2x Pentium(R) Dual-Core  CPU      E5800  @ 3.20GHz, 4.0 GiB RAM
Current user language: English (United Kingdom)

Exception = System.OutOfMemoryException
Message = Exception of type 'System.OutOfMemoryException' was thrown.
FullText = System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
   at System.Text.StringBuilder.ToString()
   at System.Windows.Forms.Control.get_WindowText()
   at System.Windows.Forms.TextBoxBase.get_WindowText()
   at System.Windows.Forms.Control.get_Text()
   at System.Windows.Forms.TextBox.get_Text()
   at MySQL.Forms.TextBoxImpl.append_text(TextBox* self, basic_string<char\,std::char_traits<char>\,std::allocator<char> >* text, Boolean scroll_to_end)
   at MySQL.MCallback3<void\,mforms::TextBox \*\,std::basic_string<char\,std::char_traits<char>\,std::allocator<char> > const \&\,bool>.cpp_callback(TextBox* a1, basic_string<char\,std::char_traits<char>\,std::allocator<char> >* a2, Boolean a3)
   at boost.function0<bool>.()(function0<bool>* )
   at TimerHandler.timer_tick(Object sender, EventArgs e)
   at System.Windows.Forms.Timer.OnTick(EventArgs e)
   at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

How to repeat:
occurs every time
[30 Jul 2012 18:01] Alfredo Kojima
Please start WB with the -log-level=debug3 command line option and repeat the bug.
After that, get the log file and attach it again. Thanks
[31 Jul 2012 8:21] Tony Medici
Hi There, 

It seems that the WB_LOG file is not being created. I do however get this text in the command window after the crash:
Unhandled Exception: System.TypeInitializationException: The type initializer fo
r 'MySQL.GUI.Workbench.ExceptionDialog' threw an exception. ---> System.OutOfMem
oryException: Exception of type 'System.OutOfMemoryException' was thrown.
   at MySQL.GUI.Workbench.ExceptionDialog.InitializeComponent()
   at MySQL.GUI.Workbench.ExceptionDialog..ctor()
   at MySQL.GUI.Workbench.ExceptionDialog..cctor()
   --- End of inner exception stack trace ---
   at MySQL.GUI.Workbench.ExceptionDialog.Show(String message, String info, WbCo
ntext wbcontext)
   at MySQL.GUI.Workbench.Program.HandleException(Object o)
   at MySQL.GUI.Workbench.Program.Main(String[] Args)

Unhandled Exception: System.TypeInitializationException: The type initializer fo
r 'MySQL.GUI.Workbench.ExceptionDialog' threw an exception. ---> System.OutOfMem
oryException: Exception of type 'System.OutOfMemoryException' was thrown.
   at MySQL.GUI.Workbench.ExceptionDialog.InitializeComponent()
   at MySQL.GUI.Workbench.ExceptionDialog..ctor()
   at MySQL.GUI.Workbench.ExceptionDialog..cctor()
   --- End of inner exception stack trace ---
   at MySQL.GUI.Workbench.ExceptionDialog.Show(String message, String info, WbCo
ntext wbcontext)
   at MySQL.GUI.Workbench.Program.HandleException(Object o)
   at MySQL.GUI.Workbench.Program.OnUnhandledException(Object sender, UnhandledE
xceptionEventArgs e)

Regards

Tony Medici
[31 Jul 2012 8:22] Tony Medici
Hi There, 

It seems that the WB_LOG file is not being created. I do however get this text in the command window after the crash:
Unhandled Exception: System.TypeInitializationException: The type initializer fo
r 'MySQL.GUI.Workbench.ExceptionDialog' threw an exception. ---> System.OutOfMem
oryException: Exception of type 'System.OutOfMemoryException' was thrown.
   at MySQL.GUI.Workbench.ExceptionDialog.InitializeComponent()
   at MySQL.GUI.Workbench.ExceptionDialog..ctor()
   at MySQL.GUI.Workbench.ExceptionDialog..cctor()
   --- End of inner exception stack trace ---
   at MySQL.GUI.Workbench.ExceptionDialog.Show(String message, String info, WbCo
ntext wbcontext)
   at MySQL.GUI.Workbench.Program.HandleException(Object o)
   at MySQL.GUI.Workbench.Program.Main(String[] Args)

Unhandled Exception: System.TypeInitializationException: The type initializer fo
r 'MySQL.GUI.Workbench.ExceptionDialog' threw an exception. ---> System.OutOfMem
oryException: Exception of type 'System.OutOfMemoryException' was thrown.
   at MySQL.GUI.Workbench.ExceptionDialog.InitializeComponent()
   at MySQL.GUI.Workbench.ExceptionDialog..ctor()
   at MySQL.GUI.Workbench.ExceptionDialog..cctor()
   --- End of inner exception stack trace ---
   at MySQL.GUI.Workbench.ExceptionDialog.Show(String message, String info, WbCo
ntext wbcontext)
   at MySQL.GUI.Workbench.Program.HandleException(Object o)
   at MySQL.GUI.Workbench.Program.OnUnhandledException(Object sender, UnhandledE
xceptionEventArgs e)

Regards

Tony Medici
[1 Aug 2012 20:12] Alfredo Kojima
Where did you look for the log file? Also, how many objects are being migrated?
[2 Sep 2012 1: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".