MySQL Bugs: #66805: wb will take longer to open sql editor after crash

Bug #66805	wb will take longer to open sql editor after crash
Submitted:	13 Sep 2012 11:40	Modified:	2 Jan 2013 12:57
Reporter:	Marcin Szalowicz	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	5.2.42, 5.2.43,5.2.44	OS:	Linux (ubuntu 12.04/amd64)
Assigned to:		CPU Architecture:	Any
Tags:	crash, long open

Description:
There is a big difference in opening connection after wb crashed. I think this bug is related to bug 66043. The sql editor is opening much longer if wb previously crashed and there is cache file in $USER/.mysql/workbench/cache for that connection.
The problem is bigger in 5.2.43 than it was in 5.2.42
There is also big chance that with so big instance and without cleaned cache directory, after wb crash.. while opening sql editor wb will segfault but it's rather rarely.

How to repeat:
1: Start wb
2: Open connection/sql editor
3: kill wb (kill -9 ...)
4: start wb (you should see some connection is auto saved)
5: open the auto-saved connection (which has got file: $USER/.mysql/workbench/cache)

now do the same but before step 4, remove files from : $USER/.mysql/workbench/cache
the sql editor/connection should open much much faster.

The behavior is more visible on instances that has got over 1k schemas, but you should see it also in small instance

Isn't crash recovery supposed to add some overhead?  And the more overhead the more there is to recover?

The real problem as I see it is that WB crashes a lot (for some users at least). No crash ==> no such problem. So I think it would be relevant if you reported the crash (if you did not already and if you still have enough details to post a meaningful report) - rather than this. :-)

Peter
(not a MySQL/Oracle person).

well yeah ... i understand that there is some overhead, but ... it should be visible only first time after wb crashed, not after every time...
and regarding crash, well i'm trying to find out what is causing the crash, but until i'll not have good test case, i'll not fill up any bug ...

Please try version 5.2.44. Thanks.

still the same ;/

fixed in 5.2.45