MySQL Bugs: #60780: Execute SQL File... doesn't work for big scripts

Bug #60780	Execute SQL File... doesn't work for big scripts
Submitted:	6 Apr 2011 14:07	Modified:	27 Jul 2012 8:48
Reporter:	Thomas Devos	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S1 (Critical)
Version:	5.2.33	OS:	Windows (Seven)
Assigned to:		CPU Architecture:	Any

Description:
Hi, 

Everything was good until this morning.

I tried to execute a sql File but this error append . 
I retried, reboot the program, my computer, my wamp local server, try another file, try to create a shcema, but nothing work !

The file is heavy : 128Mo but it worked before.

How can i do ? 

(sorry for my english, i speak french.)

My System info : 
MySQL Workbench CE for Windows version 5.2.33

Configuration Directory: C:\Users\thomas.devos.FNP\AppData\Roaming\MySQL\Workbench

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

Cairo Version: 1.8.8

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

OpenGL Driver Version: 2.1.0 - Build 8.15.10.1995

OS: Microsoft Windows 7  Service Pack 1 (build 7601), 32-bit

CPU: 4x Intel(R) Core(TM) i5 CPU         650  @ 3.20GHz, 3.4 GiB RAM

Active video adapter: Intel(R) Graphics Media Accelerator HD

Installed video RAM: 1531 MB

Current video mode: 1680 x 1050 x 4294967296 couleurs

Used bit depth: 32

Driver version: 8.15.10.1995

Installed display drivers: igdumdx32.dll,igd10umd32.dll

Current user language: Français (Belgique)

MySQL Workbench CE for Windows version 5.2.33

Configuration Directory: C:\Users\thomas.devos.FNP\AppData\Roaming\MySQL\Workbench

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

Cairo Version: 1.8.8

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

OpenGL Driver Version: 2.1.0 - Build 8.15.10.1995

OS: Microsoft Windows 7  Service Pack 1 (build 7601), 32-bit

CPU: 4x Intel(R) Core(TM) i5 CPU         650  @ 3.20GHz, 3.4 GiB RAM

Active video adapter: Intel(R) Graphics Media Accelerator HD

Installed video RAM: 1531 MB

Current video mode: 1680 x 1050 x 4294967296 couleurs

Used bit depth: 32

Driver version: 8.15.10.1995

Installed display drivers: igdumdx32.dll,igd10umd32.dll

Current user language: Français (Belgique)

How to repeat:
I cant do anything !

My error is : "error : bad location"

Thank you for the bug report. That was a restore operation of a database what you tried with the sql file?. Thanks.

Thanks for your reaction. 

It's a file who create tables and insert datas (very much datas).

In fact, i have a big database for my website and sometimes import/export from internet to my localdatabase.

But maybe the file is too big ?

Another error came to me : "ERROR OPENING FILR C:/.../myFile.sql 
Could not allocate 268435456 bytes to read file"

is the file too big ?

That is a little big, yes. Please try restoring using the File -> Execute SQL File... menu item instead of opening it in the editor?

This is a duplicate of bug #55312

Yes, it's what i do !
For the moment, i use dos command prompt but no so easy.

Sorry, I misunderstood the report then. In this case, this is not a duplicate, but a separate issue.
The problem is probably that your file is too big, we have plans for changing the implementation of the 
command for executing big files, so I'll leave this verified and change the synopsis. Please keep using the command line client as you are, for now.

I fear it is not the cause. I have the exact same problem, while my file is only 32kb.

Executing the file trough command line client goes correctly. Throws 2 errors, one is a case of being unable to create a new user and another I cannot see because there are too many messages in the command line to display it. Thus I wanted to do it trough the Workbench to use it's output pane.

Sorry for writing too many messages but I click submit too early.

After clicking Execute SQL file Workbench simply seems to go into an endless loop and freezes.

Adrian, your bug sounds different. Please file a new report with the file that causes the problem.

Fixed as of Workbench 5.2.41, and here's the changelog entry:

Loading large files (over 100MB) using "File",
"Open SQL Script..." would fail to load the
script, and throw an out of memory exception while halting
operation.

Now, MySQL Workbench warns users if a file exceeding 100MB is
attempted to be loaded, and no longer crashes when running out
of memory but instead reports that the file was unable to be
loaded.