MySQL Bugs: #61119: Out of Memory

Bug #61119	Out of Memory
Submitted:	10 May 2011 21:12	Modified:	15 Jun 2011 13:56
Reporter:	David Berg	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S3 (Non-critical)
Version:	5.2.33 CE	OS:	Windows (XP Pro SP3)
Assigned to:		CPU Architecture:	Any

Description:
I was loading an 88 mb dump file to be imported into my database when I got the error "Exception of the type 'System.OutOfMemoryException' was thrown ...

... and then I was unable to close the error message window or the Workbench.

How to repeat:
File --> Open Script --> 88 mb script file.

Thank you for the bug report. Could you please provide the output of Help->System Info. Thanks.

MySQL Workbench CE for Windows version 5.2.33

Configuration Directory: C:\Documents and Settings\David Berg\Application Data\MySQL\Workbench

Data Directory: C:\Program Files\MySQL\MySQL Workbench 5.2 CE

Cairo Version: 1.8.8

Rendering Mode: OpenGL is not available on this system, so GDI is used for rendering.

OS: Microsoft Windows XP Professional Service Pack 3 (build 2600)

CPU: 2x Intel(R) Core(TM)2 Duo CPU     E6550  @ 2.33GHz, 2.0 GiB RAM

Active video adapter: Intel(R) G33/G31 Express Chipset Family

Installed video RAM: 128 MB

Current video mode: 1680 x 1050 x 4294967296 colors

Used bit depth: 32

Driver version: 6.14.10.4837

Installed display drivers: igxprd32.dll

Current user language: English (United States)

Please, check the size of your files in the sql_history directory. See bug #58778 for the details.

Out of Memory Message

Attachment: Out of Memory.png (image/x-png, text), 41.45 KiB.

Valeriy ... I emptied the sql_history directory as suggested in Bug 58778, but the Out of Memory exception and hung Workbench persists. I submitted a file containing the exception message under separate cover and also uploaded the offending script to your FTP site as conpro_prod_dump_20110510.zip.

Is the script a dump that you want to execute? if so, please try using File -> Execute SQL File..., instead of loading it into the editor

Alfredo,
Yes, it is a script dump. Does that make a difference?

When I restarted Workbench I got the message "Saved scratch buffer 1.scratch is bigger than 4.77 MiB." Does that mean the largest script file I can edit in Workbench is 4.77 mb? This particular file is 88 mb.

MySQL Query Browser has no trouble editing a file this size. Why is there this limitation in Workbench?

When I try to File --> Execute SQL File --> Filename, Workbench just hangs.

Hello David.
The new WB version 5.2.34 is out (http://dev.mysql.com/downloads/workbench/5.2.html).
Can you please try with this new version and let us know the outcome?
Also you will like to try the "Import from Self-contained file" option in: Server Administration -> Data export and restore -> Import from Disk which I consider the better option to import a dump file.
If even with WB 5.2.34 the problem persist, can you please upload your dump file to a storage site like dropbox?
Thanks.

Armando ... both techniques worked successfully. Thank you!

I'm Glad that it help David.
Please feel free to report any other finding.
Closing defect.
Thanks.