Bug #53652 Stop Query causes WB to hang
Submitted: 14 May 2010 15:45 Modified: 21 May 2010 14:35
Reporter: Brandon Whitehead Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S1 (Critical)
Version:5.2.21RC OS:Any
Assigned to: Sergei Tkachenko CPU Architecture:Any

[14 May 2010 15:45] Brandon Whitehead
Description:
I've been using Query Browser, and it took about 5 minutes of using WB for this to pop up.

When I try to stop a query from executing (obviously would need to be one that doesn't return immediately), WB displays spinning-beachball-of-doom and hangs.  Waited several minutes before I had to force quit.

This seems intermittent, as sometimes the query is canceled, and sometimes WB hangs.  However, WB seems to hang about 75% of the time, rather than canceling the query. 

I attempted to shorten the keepalive preference from 600seconds to 30 seconds to no effect.

Back end is mysql 5.0.45 on dualcore RHEL server.

How to repeat:
Run a query with many rows.  Attempt to stop query.
[14 May 2010 17:32] Valeriy Kravchuk
What exact query you were executing? Can you send EXPLAIN results for it?
[14 May 2010 17:34] Brandon Whitehead
Several basic SELECT * FROM <table> statements. QB doesn't seem to have this problem.
[19 May 2010 20:59] Sergei Tkachenko
Recent changes in code maintaining passwords cache led to arbitrary dead-locks: find_or_request_for_password always ran from main thread what lead to unnecessary lock acquiring when only lookup is required.
Fixed by adding non-locking find_password method.
[20 May 2010 16:41] Johannes Taxacher
fix confirmed on repository
[21 May 2010 14:31] Tony Bedford
An entry has been added to the 5.2.22 changelog:

In the SQL Editor, if a query was executed, and then interrupted, MySQL Workbench hung.
[25 May 2010 9:36] Johannes Taxacher
Bug #53926 has been marked as duplicate of this one