Bug #66043 WB hangs when opening connection after crash
Submitted: 27 Jul 2012 7:09 Modified: 21 Aug 2012 16:39
Reporter: Marcin Szalowicz Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:5.2.41,5.2.42 OS:Other (Ubuntu 12.04/amd64)
Assigned to: CPU Architecture:Any
Tags: Connection, hang, workbench

[27 Jul 2012 7:09] Marcin Szalowicz
Description:
Sometimes WB will hang,  then if we kll it through kill -9, and start it again, we can see in the connection dialog that some connection are in "auto save" state. 
If we'll try to open it, WB will hang, 

this time kill -9 is working or after 2 miuntes (maybe more) wb will finally unhang.
The solution is to remove all files from $HOMEDIR/.mysql/workbench/cache/ and start WB again

Maybe it's specific, i can say that i can repeat it, every time with connection to instance that have often few hundred of schemas

How to repeat:
1: Start Workebnch, 
2: open one connection
3: open 1 query tab and type some query (don't execute it)
4: open second query tab (noo need to enter anything)
5: from terminal, kill -9 mysqlworkbench (all processes)
6: start workbench
7: try to open previously used connection (should be with suffix: "auto saved")
8: WB is freezed... for some time
[27 Jul 2012 7:24] Peter Laursen
I posted a similar thing here:
http://bugs.mysql.com/bug.php?id=66016
[1 Aug 2012 13:15] Anders Bolager
I have found out that, at lest for me, I can get around the hang by deleting the "lock" file in the C:\Users\xxx\AppData\Roaming\MySQL\Workbench\sql_workspaces directories
[14 Aug 2012 9:01] Marcin Szalowicz
5.2.42 also affected
[21 Aug 2012 16:39] Marcin Szalowicz
fixed in .42, the problem with wb hang is related now to huge schema list, over 0.1k