MySQL Bugs: #72486: Workbench crashes often on Mac OSX

Bug #72486	Workbench crashes often on Mac OSX
Submitted:	30 Apr 2014 4:15	Modified:	19 Jun 2014 1:22
Reporter:	Steve Fatula	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S2 (Serious)
Version:	6.1.6	OS:	MacOS (10.9.3)
Assigned to:		CPU Architecture:	Any

Description:
I run the app, try a query, it crashes. Previous versions before 6.1 worked for me reliably, such as 6.0.9. 6.1 series seems to be unusable, at least for me. Crashes most of the time. 

I will try and attach the Apple crash log for this.

How to repeat:
Not sure, all I do is run the app and do a query, it crashes. I do use ssh and private keys to tunnel in. If there is any other info I can provide, let me know.

Apple crash log

Attachment: WorkbenchCrash.txt (text/plain), 84.15 KiB.

Thank you for the bug report. Are you connected with remote server? Which server version?. Thanks.

Yes, remote server is Centos, MySQL is version 5.1.73

ssh tunnel

Thank you for the bug report.
This bug has got the following duplicates: bug #72507, bug #72622, bug #72619

72507 may be a duplicate, though it is a different OS. The two others appear quite related if not the same. This makes the 6.1 versions unusable as is.

Please update the status on this, as I am now running into this issue using SSH tunneling. I am using version 6.1 on Windows 7 and did not have this problem on version 5 with XP.

The problem appears to stem from Workbench sending username to server without password but the database requires the password. Log file example during connection:

[INF][     SSH tunnel]: SSH tunnel connect executed OK
[INF][     SSH tunnel]: Existing SSH tunnel found, connecting
[ERR][  GRTDispatcher]: exception in grt execute_task, continuing: Exception: Access denied for user 'daveh'@'localhost' (using password: NO)

After connecting, if I right-click a table in a schema and click Select Rows, it throws either MySQL Error 2013 (Lost connection to MySQL server) or Error 0 (no message). If I click the lightning symbol in the query tab for the select statement, it runs fine.

Sometimes it crashes the whole program, sometimes it works fine no problem, but the error in the log file is always there on connection.

It just appears the program is trying to send credentials with just username at some point and when denied thinks it is disconnected and causes erratic behavior. Please investigate this point for fix.

Just to clarify, I have the passwords stored in the vault for the Linux SSH connection and the MySQL localhost connection, and it connects just fine initially, so that is not the problem. The problem is that MySQL Workbench is passing the credentials without the password at some point afterword that is causing the denied error (notice it says using password: NO even though I have the passwords in the vault) and making it think it's lost connection even though it successfully displays all databases and schemas, so this is purely a bug.

Downloaded 6.1.6, still cannot use workbench. It's not useable, can never run it without crashing. Even the first query.

I had been commenting in Bug #72249, but am moving to this one instead.

All my crashes have happened over an SSH tunnel as well.

Here's a crash trace from when I'm attempting to connect to a database that isn't using SSL:

Thread 25 Crashed:
0   libsystem_kernel.dylib        	0x92dd2952 __pthread_kill + 10
1   libsystem_pthread.dylib       	0x93763167 pthread_kill + 101
2   libsystem_c.dylib             	0x970a129c abort + 155
3   libsystem_malloc.dylib        	0x95923dab free + 419
4   libmysqlclient.18.dylib       	0x04a6f6e5 vio_delete + 46
5   libmysqlclient.18.dylib       	0x04a4e42f end_server + 47
6   libmysqlclient.18.dylib       	0x04a4e51e cli_safe_read + 56
7   libmysqlclient.18.dylib       	0x04a502f0 cli_read_query_result + 26
8   libmysqlclient.18.dylib       	0x04a4fb84 mysql_real_query + 96
9   libmysqlcppconn.7.1.1.3.dylib 	0x049af805 sql::mysql::NativeAPI::LibmysqlStaticProxy::real_query(st_mysql*, char const*, unsigned long) + 31
10  libmysqlcppconn.7.1.1.3.dylib 	0x049b0ab5 sql::mysql::NativeAPI::MySQL_NativeConnectionWrapper::query(sql::SQLString const&) + 55
11  libmysqlcppconn.7.1.1.3.dylib 	0x049ab9e8 sql::mysql::MySQL_Statement::do_query(sql::SQLString const&) + 52
12  libmysqlcppconn.7.1.1.3.dylib 	0x049abead sql::mysql::MySQL_Statement::executeQuery(sql::SQLString const&) + 49
13  libwbpublic.be.dylib          	0x00912165 AutoCompleteCache::refresh_columns_w(std::string const&, std::string const&) + 243
14  libwbpublic.be.dylib          	0x009106aa AutoCompleteCache::refresh_cache_thread() + 300
15  libwbpublic.be.dylib          	0x00912519 AutoCompleteCache::_refresh_cache_thread(void*) + 25
16  libglib-2.0.0.dylib           	0x0012f4f5 g_thread_proxy + 161
17  libsystem_pthread.dylib       	0x937625fb _pthread_body + 144
18  libsystem_pthread.dylib       	0x93762485 _pthread_start + 130
19  libsystem_pthread.dylib       	0x93767cf2 thread_start + 34

Fixed as of the upcoming MySQL Workbench 6.1.7 release, and here's the changelog entry:

Sometimes MySQL Workbench would crash when connecting to a remote Linux host
using SSH.

Thank you for the bug report.

crash report for 6.16 on OS X 10.9

Attachment: MySQL_Workbench-crashreport-06-23-2014.txt (text/plain), 86.91 KiB.

I am seeing constant crashes on 6.1.6 as well. I am on a SSL-based VPN, but not tunneling over SSH otherwise. Crash report attached.   When will 6.1.7 be out?  This issue is making it impossible for me to get needed work done.

Lastest crash

Attachment: MySQLWorkbench_2016-08-30-121010_AdexMacBebPro.crash (application/octet-stream, text), 96.38 KiB.

Previous crash

Attachment: MySQLWorkbench_2016-08-29-172837_AdexMacBebPro.crash (application/octet-stream, text), 104.88 KiB.

Happens every day

Attachment: Screen Shot 2016-08-30 at 12.16.59.png (image/png, text), 160.52 KiB.

I like the way bugs are solved: by closing the ticket.
Version 6.3.7 still crashes frequently when running a basic select.
Context: mostly happens with large tables and remote servers.

This is definitely still a problem. Any SELECT query on a remote DB causes 6.3.7 to crash constantly, every time. Installed 6.2.5.0, no issues.

Like Wesley this is also affecting me still.

v 6.3.7
Windows 10

Hi,

I am still facing this issue on MacOS Sierra 
MySQL workbench version 6.3.8 1228 CE 64 bit Community version.

When trying to connect to remote connection and executing a simple select statement crashes the whole application.

It was present in previous versions of Workbench on Mac OS Yosemite also.
Because of this, I needed to switch other tool for fetching the data.

Time to time I need to manage the DB also, so there is no better option available to me than workbench. 

Please re-opened the bug or point to me on-going bug where I can attach the crash report again.