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: | |
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
[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