MySQL Bugs: #89475: MySQL Workbench Quits Unexpectedly After Closing a Tab

Bug #89475	MySQL Workbench Quits Unexpectedly After Closing a Tab
Submitted:	30 Jan 2018 17:33	Modified:	5 May 2018 8:41
Reporter:	Jesse Ivy	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S2 (Serious)
Version:	6.3.10 CE build 12092614 (64 bit)	OS:	MacOS (High Sierra)
Assigned to:		CPU Architecture:	Any
Tags:	bug, close, Close Tab, crash, quit unexpectedly, tabs

Description:
MySQL Workbench Community (GPL) for Mac OS X version 6.3.10 CE build 12092614 (64 bit) Quits on Mac OS X High Sierra after closing a tab when I have multiple server connections open.

How to repeat:
Typically I have several connections open with multiple tabs open in each. When I close a bunch of tabs, usually if closing the last tab (which isn't smart I guess), or when closing the last VISIBLE tab, the workbench crashes. There is no option to restore. I typically have three to five connections, and several windows.

Suggested fix:
I've noticed that sometimes it works fine and when you close the last tab a new query tab automatically opens. This seems like acceptable behavior but I wonder if the logic that automatically opens a new tab is where the bug is and if so I think that could preferably be removed and leave a blank slate instead, which is I think the more expected behavior. The user is capable of opening a tab themselves and it's not known that they are interested in writing a query. Administrators use the tool as well. I think it's nice because I'm writing queries. Thank you.

Adding version and other neglected details.

I couln't repeat on below environment, I need more information to repeat (maybe the kind of connection):

MySQL Workbench Community (GPL) for Mac OS X version 6.3.10 CE build 12092614 (64 bit)
Configuration Directory: /Users/miguel/Library/Application Support/MySQL/Workbench
Data Directory: /Applications/MySQLWorkbench.app/Contents/Resources
Cairo Version: 1.10.2
OS: macOS 10.13.x High Sierra x86_64
CPU: 4x Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz - 16.00GiB RAM
No video adapter info available

It's SSL connections both on an internal network and to servers outside our network. One of the servers which does seem most problematic requires a VPN. The worbench crashed several times yesterday, while editing SQL which is new behavior and doesn't make much sense as I'm not even executing the request. The connection which requires a VPN will often produce a broken pipe exception or something like that but a dialog or two pops up and once they are dismissed normal operation continues without a crash or any restart necessary. One final detail is that when connecting to the VPN a warning pops up stipulating my IP did not change. I'll see if I can debug the connection and review the logs for more info. Since I started recieving the popups I've stopped leaving that connection open but it doesn't seem to help. Thank you for having a look.

Thank you for the feedback.
I could not repeat this issue on various boxes(MacOS, Ubuntu, Windows7) with/without VPN connections and with/without TCP/IP over SSH connection.

Could you please provide unaltered log generated after starting WB in debug mode and when it crashes?

MySQLWorkbench --log-level=debug3 

Log files can be found in these locations:
Log File Location: ~/Library/Application Support/MySQL/Workbench/logs

System crash logs generated for Workbench are in ~/Library/Logs/DiagnosticReports/MySQLWorkbench*

Similar issue was observed in Bug #84405 which was marked as duplicate of Bug #83658 and which is fixed.

Regards,
Umesh

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

I also today cannot connect anymore even to docker. I double click on connection rectangle and mysql workbench closes.

Log:

14:53:50 [INF][   WBContext UI]: Initializing workbench context UI with these values:
	base dir: /usr/share/mysql-workbench
	plugin path: /usr/lib/mysql-workbench/plugins
	struct path: /usr/share/mysql-workbench/grt
	module path: /usr/lib/mysql-workbench/modules
	library path: /usr/share/mysql-workbench/libraries
	user data dir: /home/darius/.mysql/workbench
	open at start: 
	open type: 
	run at startup: 
	run type: 
	Force SW rendering: No
	Force OpenGL: No
	quit when done: No
14:53:50 [INF][      WBContext]: WbContext::init
14:53:51 [INF][            WBA]: Looking for extension modules for WBA...
14:53:51 [INF][            WBA]: 0 extension modules found
14:53:51 [WRN][            grt]: /home/darius/.mysql/workbench/connections.xml:25: link '66c6f07f-e679-11e8-a12b-e89a8fe9e73f' <object GrtObject> key=owner could not be resolved
14:53:51 [INF][      WBContext]: System info:
 	MySQL Workbench Community (GPL) for Linux/Unix version 6.3.10 CE build 12092614 (64 bit)
	Configuration Directory: /home/darius/.mysql/workbench
	Data Directory: /usr/share/mysql-workbench
	Cairo Version: 1.14.6
	OS: Ubuntu 16.04 x86_64
	CPU: 2x Intel(R) Pentium(R) CPU B960 @ 2.20GHz (1025.832MHz) - 7.65GiB RAM
No video adapter info available
	Distribution: Ubuntu 16.04.4 LTS

	Fips mode enabled: no

14:53:51 [INF][    WQE backend]: Found auto-save workspace /home/darius/.mysql/workbench/sql_workspaces/Local_instance_3306-1.autosave
14:53:51 [INF][    WQE backend]: Found auto-save workspace /home/darius/.mysql/workbench/sql_workspaces/Vop_docker-1.autosave
14:54:08 [ERR][    Preferences]: Logger set to level 'debug3' in Preferences menu
14:54:09 [DB2][            grt]: wb.form.showOptions finished in 5.97s
14:54:12 [DB3][SQL Editor Form]: Creating KeepAliveInterval timer...
14:54:12 [DB1][ mforms backend]: Looking up password for 'root'@'Mysql@127.0.0.1:33306' has succeeded
14:54:12 [DB3][    WQE backend]: Connecting SQL editor...
14:54:12 [DB3][       GRT task]: Sending task "execute sql queries" to dispatcher (wait)...
14:54:12 [DB1][  GRTDispatcher]: starting worker thread
14:54:12 [DB1][  GRTDispatcher]: worker thread running
14:54:12 [DB3][  GRTDispatcher]: Running task "execute sql queries"
14:54:12 [DB2][SQL Editor Form]: Notifying server state change of Mysql@127.0.0.1:33306 to running
14:54:12 [INF][SQL Editor Form]: Opened connection 'Vop docker' to MySQL Community Server (GPL) version 5.7.23
14:54:12 [DB1][      WBContext]: Saved connection list (MySQL: 2)
14:54:12 [DB3][    WQE backend]: Connection to SQL editor succeeded
14:54:12 [DB3][  GRTDispatcher]: Task "execute sql queries" finished
14:54:12 [DB3][       GRT task]: Sending task "Live Schema Refresh Task" to dispatcher (don't wait)...
14:54:12 [DB1][  GRTDispatcher]: starting worker thread
14:54:12 [DB3][MySQL Name Cache]: Creating worker thread
14:54:12 [DB1][  GRTDispatcher]: worker thread running
14:54:12 [DB2][  column_widths]: Using column width cache file /home/darius/.mysql/workbench/cache/Vop_docker.column_widths
14:54:12 [DB3][  GRTDispatcher]: Running task "Live Schema Refresh Task"
14:54:12 [DB2][MySQL Name Cache]: Entering worker thread
14:54:12 [DB3][MySQL Name Cache]: Updating schema listSaved connection list (MySQL: 2)
14:54:12 [DB1][      WBContext]: Saved connection list (MySQL: 2)
14:54:12 [DB2][MySQL Name Cache]: Leaving worker thread
14:54:12 [DB2][SQL Editor Form]: Updating SQL menu and toolbar
14:54:12 [DB2][SQL Editor Form]: Updating SQL menu and toolbar
14:54:12 [DB2][SQL Editor Form]: Updating SQL menu and toolbar

Weird thing that this looks like started happening after I had to power of my PC with physical button because it was not responding.