MySQL Bugs: #74179: Some Query Tabs can't be closed

Bug #74179	Some Query Tabs can't be closed
Submitted:	1 Oct 2014 14:52	Modified:	12 Mar 2016 14:05
Reporter:	Takahito Torimoto	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S3 (Non-critical)
Version:	6.2.3.12313 build 2282	OS:	MacOS
Assigned to:		CPU Architecture:	Any
Tags:	close, Query Tab

Description:
After a while (or maybe after opening X number of Query Tabs), some (not all) Query Tabs can't be closed at all.  The 'X' mark on the Tab, or right-click and 'Close Tab' doesn't work.  Even trying 'Close Other Tabs' from a different Tab does not close the 'broken' Tabs (while closing the 'unbroken' Tabs - leaves all the 'broken' tabs open).  The only way to "fix" it is to quit MySQL Workbench and re-open it.

How to repeat:
Not exactly sure - but seems it's either related to having MySQL Workbench open/used for a while, or hitting a certain number of Tabs (or certain number of Tabs open/close actions).  It does not take that long (less than 2 days) for it to appear though.

Suggested fix:
Close (choosing 'X' on the tab, 'Close Tab' or 'Close Other Tabs' context menus) should work... :-)

Thank you for the bug report. I need here a more accurate description of the issue, the tabs opened queried a server and what status the connection is? (server up or shutdown and started again?) all the time connected, the connection timeout was applied? . Actually how long the tool presents the issue >= 2 days?. Thanks.

Server is connected.  I can create a Query Tab with the same exact Query and run it, and close it.
Actually I just realized, if I re-run the query of the "broken" tabs (running the query works), I am able to close the tabs after the query is done.

Thank you for the feedback.

I couldn't repeat with 6.3.6 version running on El Capitan, please try it. Thanks.

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".