Bug #1587 WinMySQLadmin overloads windows 2000 pagefile
Submitted: 17 Oct 2003 9:40 Modified: 17 Oct 2003 9:52
Reporter: Stephen Case Email Updates:
Status: Closed Impact on me:
Category:MySQL Server Severity:S2 (Serious)
Version:4.0.4-beta-max-nt OS:Windows (Windows 2000)
Assigned to: CPU Architecture:Any

[17 Oct 2003 9:40] Stephen Case
In short I have MySQL Server 4.0.4-beta-max-nt running on a Windows 2000 Professional Workstation, all the latest Updates and Service Packs.

MySQL Service is set to autostart along with a Shortcut in my Startup menu for WinMySQLadmin.

The problem: If I stop the MySQL Service but leave WinMySQLadmin utility running in the Icontray, over a period of about an hour it will overflow my system Pagefile and if it goes unattended after windows starts generating the pagefile errors the system will eventually become unresponsive and will need rebooted.

How to repeat:
Stop the MySQL Service but leave WinMySQLadmin utility running in the Icontray. Pull up the Windows Task Manager and Select the Performance tab. Sit back and watch as your Memory Usage slowly go through the roof.

Suggested fix:
I don't fully understanding the underlying problem with WinMySQLadmin because I haven't personally stepped through the source. But as a developer from what I have seen WinMySQLadmin is running a function periodically that is designed to check the status of the server. My guess is that an object(s) is being created when WinMySQLadmin trys to connect to the server; however, the object is not destroyed when the error is received that MySQL is not available.
[17 Oct 2003 9:52] MySQL Verification Team
Yes actually the version you are using 4.0.4-beta that tool presented
that problem. Please upgrade for a new release.