MySQL Bugs: #68403: Open connection to start querying crashes workbench

Bug #68403	Open connection to start querying crashes workbench
Submitted:	16 Feb 2013 13:51	Modified:	21 Feb 2013 20:20
Reporter:	László Somogyi	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	5.2.46, 5.2.47	OS:	Windows (Windows 8 x64)
Assigned to:		CPU Architecture:	Any

Description:
When i try to open a connection, the whole program crashes. Everything else works: EER model, Server admin

If i downgrade to 5.2.45 then there is no problem with this, so i don't think its my fault.

I connect to localhost throught 3306 with root user with a password, nothing fancy.

How to repeat:
Add a connection in the left column (Home tab)
Dobule click on the created conenction

After double clicking on the connection, this happens and doesn't go away without force.

Attachment: connectioncrash.jpg (image/jpeg, text), 125.35 KiB.

Same for me, same OS, 2 different connections both cause the program to freeze.

Could you please provide languages/windows flavor you are using?

and provide details on connection config you used?...locally , remote? 

Thank you for your interest in MySQL.

Windows 8 Pro 64bit (English)

Fairly standard (TCP/IP, port 3306) connections to 2 different remote machines (one is on a VM on my computer.)

I didn't try 5.2.46, but on 5.2.47 my screen looked just like the screenshot László provided - the connection has been made and it starts to load, but then gets stuck.

Similar to him, uninstalling and then re-installing 5.2.45 worked. (Thanks for the tip László)

As i wrote in my initial description, it is full localhost, everything default except password. The only thing i forgot to say, im running Mysql 5.5 server. Everything else is in the private comment i think. OS lang is hungarian.

Well. I checked the new setting "Create new tabs as Query tabs instead of File", not it doesn't crash. When i uncheck the box, then it continues to work too. 

So i think its an upgrade bug. If you upgrade from a version, where this setting didn't exist, the new version will crash, because it doesn't fall back to a default or something like this.