MySQL Bugs: #61459: Execute SQL File freezes Worlbench

Bug #61459	Execute SQL File freezes Worlbench
Submitted:	9 Jun 2011 10:23	Modified:	9 Jun 2011 14:54
Reporter:	Adrian Sta„czak	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	5.2.33 CE	OS:	Windows (Win 7)
Assigned to:		CPU Architecture:	Any

Description:
Execute SQL file option seems to make Workbench go into an endless loop and freeze.
No error messages or anything. The program simply isn't responding.
File isn't big, has only 32KB.
Company policy doesn't allow me to place the file.
I can only say it was created using the forward engineer option, with the option of DROP SCHEMAS turned on. After that it creates multiple databases, and tables with connections to each other (some of the between databases).
It also creates one view and one routine and has quite a few inserts.
Also it is supposed to create one Role and one User. And while the role is created properly, the create user statement always throws an error. Thus I marked an option not to export users. But the freeze still happens. No matter what changes I make. I even tried to make a new file.
I tried a completely different smaller file with one Database and a few test tables and some connections between them and the same thing happens. Without any inserts, views or routines or drop statements. Whatever files I use it freezes. The scripts run perfectly fine when used trough command line prompt (with the "source" command).
It is a serious error, tough the scripts can run using the command line client.

How to repeat:
Run an Execute SQL file function with Workbench on Windows 7, MySQL Server Version 5.5.11, Workbench version 5.2.33 CE. In my case this is ANY .sql file generated by Workbench Export -> Forward Engineer option.
Server settings are for a Developer Machine (low memory).
As I indicated before the freezing problem only arises for MYSQL Workbench, and everything runs properly and with no errors when the script is run from the command prompt's "source" command.

Suggested fix:
I have no idea other than to look trough the procedure in Workbench and checking what does that procedure do differently from Command Prompt "Source" command.

Please, check if the same problem happens with a newer version, 5.2.34. If it does,
please, send the output of Help > System Info menu item.

Check also history file size as described in last comments to Bug #58778.

Thank you. I just installed Workbench downloading the new version a few days ago. Didn't know there would be a new version so soon. There was a problem with msi installer as it didn't want do download and update applications, but I did it manually.
Now the Workbench Execute sql file runs properly.
Thanks again.

Closing according last comment from reporter. Thanks for the feedback.