Bug #63813 Opening large 200+mb backup file
Submitted: 20 Dec 2011 19:09 Modified: 2 Feb 2012 11:17
Reporter: Tyge Goodfellow Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version:5.2.36 OS:Windows (Windows 7 x64)
Assigned to: CPU Architecture:Any

[20 Dec 2011 19:09] Tyge Goodfellow 
Description:
Opening a large 205mb SQL backup in the SQL Editor caused Workbech to crash.

How to repeat:
Open the backup script.

Suggested fix:
I increased the memory setting in the Editor preferences to 134217728 bytes which is what the original error message said it couldn't allocate to open the backup file.  When attempting to use the Open large SQL backup file button from the tool bar, nothing happens.
[20 Dec 2011 19:44] Valeriy Kravchuk 
Please, try to use File > Execute SQL File... menu item. You'll probably need many times * 200M of memory to load this file in SQL editor, so this is hardly practical.
[20 Dec 2011 20:24] Tyge Goodfellow 
Hello Valeriy,

I tried that option first, to Execute SQL... from the File menu, however, the interface doesn't show any activity or results after selecting the SQL file.  Nothing happens at all when I do this.  I've opened Server Status and have watched my connection and no activity is occurring.  I'm running Windows 7 Ultimate with 8GB of RAM so I'm not concerned with the memory utilization.  Is there a way to increase the amount of memory allocated to the SQL editor to allow me to open the script?  I've tried increasing the buffer size to 256MB without result.
[27 Dec 2011 9:10] Valeriy Kravchuk 
See bug #60780 also.
[2 Jan 2012 11:17] MySQL Verification Team 
Please check http://bugs.mysql.com/bug.php?id=60780 as duplicate. Thanks.
[3 Feb 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".