MySQL Bugs: #81018: Repeatedly pressing Ctrl-W crashes Workbench

Bug #81018	Repeatedly pressing Ctrl-W crashes Workbench
Submitted:	8 Apr 2016 23:07	Modified:	11 Apr 2016 14:40
Reporter:	Shawn Heisey	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	6.3	OS:	Windows (Windows 7 x64)
Assigned to:		CPU Architecture:	Any

Description:
I had a bunch of things open in WorkBench.  I wanted to close all queries and servers, so I started pressing Ctrl-w.  On about the third keystroke, I got the "MySQL Workbench encountered a problem" popup.

How to repeat:
Open Workbench.  Open at least one server. View the connection list.  Open a table for viewing (the option that pulls up to 1000 rows).

Start pressing Ctrl-W to close things down.  Eventually the error will likely show up.

Possibly relevant info on the "problem" dialog:

Value cannot be null.
Parameter name: value

More detailed info:

On the server tab, I had two sub-tabs open -- "Query 1" and a "Select rows" view of a table.  After pressing Ctrl-W twice, both of those sub-tabs were closed and I was looking at a dark blue window.  At that point, pressing Ctrl-W again brings up the error.

Hello Shawn,

Thank you for the report.
I assume you are still using WV version < 6.3.5. I'm not seeing this issue with WB 6.3.6 on Win7. Please try latest WB version and let us know if you are still having this issue. This is likely duplicate of Bug #77906, which is fixed as part of MySQL Workbench 6.3.5 release, and here's the changelog entry:

Executing Control + W to close all tabs, and then executing it again (with
all tabs already closed), would emit a Null Pointer Exception.

Thank you for the bug report.

Thanks,
Umesh

I'm running 6.3.4.  The "Check for Updates" option on the Help menu said I was running the most current version, but when I went to mysql.com, clearly it wasn't the newest version.

With 6.3.6, there is no more error.

I would like an easy way to close the whole program, including all open tabs and connections, *without* saving the current tab state -- I don't want it to remember anything that I've opened or queries that I have typed.  This is why I am explicitly closing things, rather than just doing Alt-F4 on the whole program.