MySQL Bugs: #66016: WB hangs forever when opening 2nd or higher connection after install

Bug #66016	WB hangs forever when opening 2nd or higher connection after install
Submitted:	26 Jul 2012 7:56	Modified:	7 Aug 2012 5:07
Reporter:	Peter Laursen (Basic Quality Contributor)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.2.41CE	OS:	Windows (7/64)
Assigned to:		CPU Architecture:	Any
Tags:	qc

Description:
Defining a connection to local server 5.1.63.  'default database' set to Information_Schema. 'Test connection' is successful.  Trying to open hangs forever.  There are only a dozen very small tables on this server.

(Assuming that same problem would occur with Perfromance_Schema as well if server is 5.5.+)

How to repeat:
see above

Suggested fix:
It is perfectly valid to have I_S as default database ("USE Information_Schema;" is a valid statement)

dialog that hangs

Attachment: hangs.jpg (image/jpeg, text), 36.27 KiB.

OS is Win7

This does NOT happen to me on Mac OS X (with 5.1.64 and both I_S and P_S as default schema) and on Windows XP (with 5.5.25 and both I_S and P_S as default schema).

I tried again and now it opens.

It is reproducible! *almost* consistently.  But not quite as I thought. Probably it is not related to I_S as default database at all.

I have 3 stored connections (to local 5.1 and 5.5 servers - see the image i already uploaded).
1) open one
2) open another.  It hangs.
3) close the hanging dialog.
4) repeat step 2.  Now it opens (mostly).

It is reproducible in +50% of attempts for me like this if (and *ONLY* if) the program is freshly started.  Once a connection has been successfully opened once it does not happen (not frequently at least) any more.

Also if I have 2 connections open already, opening the 3rd may fail a similar way.  And in one case the the failure happened with the first connection opened.

I cannot provoke this error after rebooting the system. So I see two options:

1) A problem here
2) WB requires a system reboot to work reliably.

Does this happen with I_S only? Did you try other DBs?

I think I have explained in my previous posts.

I experienced this first time when opening a connection that had I_S as default database. I thought that was why.  But found later that it would happen often when opening 2nd or higher connection. It also happened with the two other connections that don't have I_S as default database.  Once it also happened while opening the first connection. Note taht it only happened *once* for every connection. In next attempt connection openened.  But after restarting WB I could start all over getting this error.

I changed the synopsis to "WB hangs forever when opening 2nd or higher connection after install" accordingly to my later findings

The history is: I had my system turned off during night.  In the morning after booting the PC and after ½ hour of checking mails etc., I upgraded from WB .40 to .41 and the problem occurred consistently as I have described. After rebooting the system at lunchtime I tried to reproduce with no luck. 

(I have had all 5.2.x versions released since May 2010 on this system)

So as a wrote in my last post I think we must conclude:

1) Either there was an issue with my system that was solved by the reboot.
2) Or this is only happening if system has not been rebooted after upgrade to .41

something similar here http://bugs.mysql.com/bug.php?id=66043

Experienced something very similar.

Upgraded from < .41 to = .41 on 2012-07-26.  First run post upgrade ran fine.  I also turn my computer off at the end of work day.  Upon first boot next day (2012-07-27 --- Win 7/64) and running of workbench experienced similar hanging screen; unable to load any schema.  Closing and restarting of program did not alleviate issue.

Finally rebooted operating system, and re-ran Workbench.  All is fine.  Appears re-boot alleviates issue.  

If nothing else, verification that this issue has occurred more than once

I can reproduce this on one of my several test systems. For me it's not related with using I_S as default.
On my specific system I found saving the passwd in the connection profile lets me connect successfully every time. As soon as I clear the passwd and enter it on each connection-attempt, i can reproduce the reported issue.

OK! :-)

Yes .. it seems that the nature of this problem is somewhat random/non-deterministic.  Probably not easy to identify exactly what the reason is and what the fix is.  Good luck with digging into that!

Bug #66092 is a duplicate

Fixed as of the upcoming 5.2.42 release, and here's the changelog entry:

After upgrading to MySQL Workbench 5.2.41, MySQL Workbench would freeze
if the initial load involved a connection without a saved
password.