MySQL Bugs: #61443: Application Hungs when repeatedly clicking on "execute query"

Bug #61443	Application Hungs when repeatedly clicking on "execute query"
Submitted:	8 Jun 2011 15:39	Modified:	12 Jul 2011 21:27
Reporter:	Fabián Rosell	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S1 (Critical)
Version:	5.2.34 CE rev 7780	OS:	Windows (7)
Assigned to:		CPU Architecture:	Any

Description:
Application Hungs when repeatedly clicking on "execute query". Must kill program and restart to use it again.

How to repeat:
Click several times per second in any query. Application will hung for sure.

Thank you for the bug report. The application hangs even with a query you expect small dataset result?. Provide the output of Help->System Info. Thanks.

Help > System info

Main screen "Can't write to SQL History File"

Right small screen:

MySQL Workbench CE for Windows version 5.2.34

Configuration Directory: C:\Users\Fabián\AppData\Roaming\MySQL\Workbench

Data Directory: C:\Program Files (x86)\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: 3.3.0

OS: Microsoft Windows 7  (build 7600), 64-bit

CPU: 2x Intel(R) Pentium(R) D CPU 2.80GHz, 3.3 GiB RAM

Active video adapter: NVIDIA GeForce 8400GS

Installed video RAM: 512 MB

Current video mode: 1600 x 900 x 4294967296 colors

Used bit depth: 32

Driver version: 8.17.12.6724

Installed display drivers: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um

Current user language: Spanish (Argentina)

Hello Fabián.
Can you please check the size of your history file just after you get the error? (C:\Users\Fabián\AppData\Roaming\MySQL\Workbench\sql_history).
Thanks.

"This folder is empty" (C:\Users\Fabián\AppData\Roaming\MySQL\Workbench\sql_history)

Workbench folder around 5mb.

PD: explorer is set to show all hidden and system files.

Hello Fabián.
This can be related to a known "special character" problem that dev team is working on to fix next release, would you mind to create a new user without special characters in your windows box and try to reproduce the error?
Thanks a lot in advance.

Which problem? The History or the application hungs? Maybe with the former, but not with the latter, because if you "space" your executions in time, application does not hung.

I has not be able to reproduce this, can you please attach a dump of your DB and let us know the query that you are using to reproduce it?
Thanks.

Query:

-- EDIT `test`.`dummytable`

select * from dummytable

I'm attaching the database dump.

I run the query early in the morning. It didn't fail. After several hours of working (not using the workbench), I suddenly maximize it from the taskbar, and clicked "execute" (the first lightning) several times. Workbench hungs. This happens not only in the attached DB, I'm attaching the DB on your request.

Regards.

Hungup screen

Attachment: Hungup.png (image/png, text), 126.81 KiB.

Dump file

Attachment: dump.sql (application/octet-stream, text), 2.12 KiB.

Still can't reproduce it.
What is your MySQL version/Service Name/Port?
Is this a remote or Local MySQL server?
If it is remote, can you please provide the connection configuration that you are using?
Thanks in advance.

- MySql Version : 5.2.34 rev 7780 (yesterday latest, I haven't checked for updates today)
- Server is local.
- Default configuration is used (port 3306)

Just for testing, I've already hanged it up now. 

You must do "furious" clicking, don't wait for query to finalize, simply performs several frenzy clicks in line 'till it hungs up. Perhaps you may perform the test in a "far from ideal" machine (eg: slightly crappy computer, a couple of years old). 

I will try this test in my home computer (on ~7, 8 hours from now), that is far more powerful than this, and I will let you know the results.

I tried now on VM XP machine with limited resources and still can't repeat.

I'm sorry I can't help you further...

It's almost simple to me to hung it this way...

As a programmer, I would block the button at the first click, and / or clean the Application.DoEvents queue (supposing it's being programmed in .Net Framework, to "clean" possibly pending clicks). Then when query ends or it's cancelled, re-enable it. Or a thread issue.

I suppose you're already doing something like that.

What if you let the Workbench be minimized for a couple of hours, and then, suddenly, maximize it and perform the clicking? (you should keep using the computer) That is as I always hung it.

My computer died a couple of days ago. I have to reinstall Win 7. 

The surprise is, the easyness to hung up workbench is gone now. I can't reproduce the issue.

The only different thing I made in this reinstall, is installing a different version of Windows (Professional vs. Ultimate, which is running now).

I can't realize what is different now...

Thank you for the feedback.