Bug #61331 Workbench on Mac complains when opening multiple connections
Submitted: 27 May 2011 21:47 Modified: 19 Aug 2011 1:33
Reporter: Philip Tsai Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version:5.2.34 OS:MacOS (10.6.7, 10.7.x)
Assigned to: CPU Architecture:Any

[27 May 2011 21:47] Philip Tsai
Description:
This problem starts to occur more frequently in 5.2.33 compared to previous version and now consistently occurs in 5.2.33b on Mac. 

Whenever the Workbench starts, opening the second connection on (remote or local, same or different connection) would give "Error to Connect" problem. However, validating the connections all works without problem. Initially, I was about to downgrade to previous Workbench version, but then I found an odd workaround: As long as I open, say, "Help -> MySQL.com website" to get the workbench to open a separate page, opening the second (and subsequent) connection then work without problem. 

It's annoying and consistently happening in 5.2.33b.

(See http://forums.mysql.com/read.php?152,415731,415731#msg-415731 for more details)

How to repeat:
1) Open Workbench
2) Open a connection to start querying
3) Open another connection (remote or local, same or different connection - doesn't matter)
[28 May 2011 7:46] Valeriy Kravchuk
Please, check if the same problem still happens with a newer version, 5.2.34.
[3 Jun 2011 7:02] Philip Tsai
Yes, same problem in the latest 5.2.34.
[7 Jun 2011 16:30] Valeriy Kravchuk
What server version, 5.x.y, are you working with? Please, send also the output of Help > System Info menu item.

I do not see this problem on:

MySQL Workbench CE for Mac OS X version 5.2.34
Configuration Directory: /Users/openxs/Library/Application Support/MySQL/Workbench
Data Directory: /Applications/MySQLWorkbench.app/Contents/Resources
Cairo Version: 1.9.1
Rendering Mode: OpenGL is available on this system, so OpenGL is used for rendering.
OpenGL Driver Version: 2.0
OS: Darwin 9.6.0
CPU: 2x Intel(R) Core(TM)2 Duo CPU     T9400  @ 2.53GHz, 4.0 GB RAM

while connected to local 5.5.x server. Workbench spends a lot of time connecting (known bug reported elsewhere), but then 2, 3 or even 4 connections work without any complains.
[14 Jun 2011 6:28] Philip Tsai
I connect to both 5.1.50 and 5.0.77.

Here is the relevant piece from Help -> System Info:
MySQL Workbench CE for Mac OS X version 5.2.34
Configuration Directory: /Users/philip/Library/Application Support/MySQL/Workbench
Data Directory: /Applications/MySQLWorkbench.app/Contents/Resources
Cairo Version: 1.9.1
Rendering Mode: OpenGL is available on this system, so OpenGL is used for rendering.
OpenGL Driver Version: 2.0
OS: Darwin 10.7.0
CPU: 4x Intel(R) Core(TM) i7 CPU       M 620  @ 2.67GHz, 8.0 GB RAM

BTW, you may want to solicit the same info from the other user that also experiences the same problem (refer to the forum discussion link I posted in the original report).
[17 Jun 2011 7:22] Alfredo Kojima
Is the problem in 5.2.34 exactly the same as in 5.2.33? When the error happens, can you take a screenshot of the error dialog and upload to this bug?
[17 Jun 2011 7:44] Philip Tsai
Yes, exactly the same.  You can see from the picture that I am trying to open to localhost second time yet it fails.
[20 Jun 2011 16:47] Johannes Taxacher
can you please provide the crash-reporter files from your machine concerning the crashes on WB?
you should be able to find them in ~/Library/Logs/CrashReporter/
thanks
[21 Jun 2011 1:06] Christopher Gervais
FWIW I can reproduce this bug consistently with 5.2.34 (7780) running on Mac OS X 10.6.7 (10J869) when connecting to MySQL 5.1.45. What other information can I provide to help troubleshoot this issue?
[21 Jun 2011 1:09] Philip Tsai
This bug doesn't result in crashes.... Are you trying to get at all crash files up to now?
[28 Jul 2011 4:23] Valeriy Kravchuk
Bug #61989 was marked as a duplicate of this one.
[19 Aug 2011 1:33] Alfredo Kojima
This is a duplicate of bug #59520
As a workaround, delete or temporarily move aside the files in ~/Library/Application\ Support/MySQL/Workbench/sql_history/ until this issue is fixed.