Bug #53520 loading SQL dump file into DB crashed system
Submitted: 9 May 2010 15:11 Modified: 10 Jun 2010 14:16
Reporter: Graham McDermott Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.2.16 Rev 5249 OS:Windows
Assigned to: CPU Architecture:Any

[9 May 2010 15:11] Graham McDermott 
Description:
Exception = System.OutOfMemoryException
Message = Exception of type 'System.OutOfMemoryException' was thrown.
FullText = System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
   at System.String.Replace(String oldValue, String newValue)
   at MySQL.?A0x8e6a07a1.NativeToCppString(basic_string<char\,std::char_traits<char>\,std::allocator<char> >* , String str)
   at MySQL.Grt.Db.Sql.Sql_editor.sql(String sql)
   at MySQL.Grt.Db.Sql.SqlEditor.CheckSyntax()
   at MySQL.Grt.Db.Sql.SqlEditor.BackgroundActionTimer(Object obj, EventArgs args)
   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:
Using OSS workbench to load a large SQl file that I had as a backup - it failed to load with the error above.

Stop - restart OSS Workbench , error repeats.
[9 May 2010 17:53] Valeriy Kravchuk 
What exact version of MySQL Workbench, 5.2.x, do you use? How large is the dump file?
[9 May 2010 17:57] Graham McDermott 
version 5.2.16 revision 5249 according to Help->about

File was anything from 20-30MB - a number of files failed. 

We removed a set of updates that were large updates to a single table and the DB loaded so I think it was related to the single table updating.
[10 May 2010 14:16] MySQL Verification Team 
Please try version 5.2.20. Thanks in advance.
[10 Jun 2010 23: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".