MySQL Bugs: #53021: Closing the Query Editor blocks Application endlessly

Bug #53021	Closing the Query Editor blocks Application endlessly
Submitted:	21 Apr 2010 9:43	Modified:	27 Apr 2010 13:39
Reporter:	Mike Lischke	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S1 (Critical)
Version:	5.2.19+	OS:	Windows
Assigned to:	Sergei Tkachenko	CPU Architecture:	Any

Description:
Under certain circumestances closing the query editor causes Worbench to stop responding to any user input. The application is blocked and can only be killed by the taskmanager or similar tools.

How to repeat:
Create a connection in Workbench that uses a named pipe. Give it a name other than the default. Open that connection in WQE (the server must be configured to use named pipes and which pipe name to use, of course). No problems so far, one can work as usual. Now close the tab (e.g. click on the close cross in the tab). The editor disappers but from now on WB is unresponsive. Hitting that road block in an unlucky moment can make you even lose data.

WB works fine with normal TCP/IP connections.

Suggested fix:
n/a

fix confirmed in repository

An entry has been added to the 5.2.20 changelog:

If SQL Editor was using a named pipe connection, and the SQL Editor tab was closed, then MySQL Workbench stopped responding to user input and had to be killed using the Task Manager.