Bug #51601 Workbench "leaks" processes when using Admin

Description:
When launching an "Admin" window for a local server on Windows, Workbench starts a process that runs cscript.exe (at a guess - one of the VB Scripts in the install directory to gather CPU usage etc.).

When you close the admin window, the process still runs. 

Open another admin window, and another process starts.

Eventually, you can end up with many processes parented by Workbench, 

How to repeat:
1. Start Workbench.
2. Open a "Server Administration" tab for a server running on the local host. 
3. Using Process Explorer or similar, note that a new process is started, parented by Workbench.
4. Close the Server admin tab.
5. Repeat from step 2. Note that new processes are started, but old ones are never closed.

Suggested fix:
When an admin tab is closed, the process to gather CPU etc. information should be killed.

A screenshot from Process Explorer. When this was taken, five admin tabs had been opened and subsequently closed.

Attachment: WB Subprocess.png (image/png, text), 256.11 KiB.

WB Process

Attachment: wb-process.png (image/png, text), 12.15 KiB.

Thank you for the bug report. Verified as described.

Ver 5.2.18 Rev 5625
Windows Xp SP3

Error is associated but diplaying slightly different results.

The CSRIPT blank 'window' remains open in the background.

I presume a polling action between the now 2 windows, causes a flashing effect every 2 secs - closing the CSRIPT window does NOT stop the flashing rendering the workbench UNUSABLE.

Paul

Leaking cscript was fixed.

Admin Tab Closing Error

Attachment: mysql-WB-Error.PNG (image/x-png, text), 5.60 KiB.

The above error occurs if the cscript window is closed and then you attempt to close the 'admin' tab

Leaking processes was fixed. The bug related to windows xp and visible cmd window should be moved to a new bug.

fix confirmed in repository

An entry has been added to the 5.2.20 changelog:

Each time an Admin tab was started an instance of cscript.exe was executed. However, when the Admin tab was closed the corresponding cscript.exe process was not terminated. This resulted in ever increasing numbers of cscript.exe processes, which consumed resources unnecessarily, and constituted a resource leak.