MySQL Bugs: #72310: Workbench Crash on remote connection

Bug #72310	Workbench Crash on remote connection
Submitted:	10 Apr 2014 19:19	Modified:	3 Jun 2014 20:38
Reporter:	Marcelo Zucareli	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	6.1.4	OS:	MacOS (10.9.2)
Assigned to:		CPU Architecture:	Any
Tags:	random crash

Description:
When i do a simple SELECT * FROM database.TABLE on a remote server, workbench sometimes execute correctly or return random errors or crash and close. The random erros when execute the same SQL are: 

1) Error Code: 0 
2) Error Code: 0 MySQL_ResultSet::getString: invalid value of 'columnIndex'
3) Error Code: 1044 Access denied for user 'user'@'%%' to database '<TableName>' 

These errors occurs only when connecting to remote servers, the third message is very strange, because workbench tried to connect to a table instead of a database. Weird! 

How to repeat:
Connect to a remote server with wifi or unstable connection, write SELECT * FROM <database>.<table> and execute the query. 

Suggested fix:
Maybe these errors occurs because of a network connection exception.

This is an annoying problem of the latest Mac OS release which makes it very difficult to use this version. I've made the experience that the problem persists even after a restart of the workbench. I had to connect and disconnect to the server, quit the application and close query tabs several times to make the query causing the crash work again, but the problem not seems to be deterministic/reproducible. I can attach a crash report if that would help.

I have the same issue using MySQL Workbench 6.1.6/OSX 10.9.3 and can provide error logs if needed. I only see issues 1+2, not 3. Connecting to remote servers.

I've made the experience that sometimes the only way to make a "crashing" query work again is to send a different query to the server first.

duplicate of bug #72486