Bug #23199 Memory Leaks
Submitted: 12 Oct 2006 7:38 Modified: 4 Jan 2007 10:51
Reporter: Alexander Holodny Email Updates:
Status: Won't fix Impact on me:
None 
Category:MySQL Query Browser Severity:S3 (Non-critical)
Version:1.2.4 beta OS:Windows (Windows XP SP2)
Assigned to: Mike Lischke CPU Architecture:Any
Tags: leaks, Memory

[12 Oct 2006 7:38] Alexander Holodny 
Description:
According to "Windows Task Manager", after couple of hours of QB usage, it reserved for use 472 MB of swap-mem.
screenshot here: http://mirik.net.ua/~halic/qb-mem-leeks.jpg

How to repeat:
dont restart until ~10 hours.

Suggested fix:
use c#.
MONO can start a lot of binaries generated by MS/.NET compiler.

NuMega BoundsChecker is also a usefull thing.
[12 Oct 2006 19:30] Sveta Smirnova 
Not enough information was provided for us to be able to handle this bug. Please re-read the instructions at http://bugs.mysql.com/how-to-report.php

If you can provide more information, feel free to add it to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.

I can not repeat just by staying open MySQL QUery Browser for more than 10 hours.
[14 Oct 2006 10:08] Alexander Holodny 
just write query like "select * from mysql.user" or anything else, and hold down crtl+enter keys until 10 minutes.
my result is at screanshots. it is near 948 MB of "VM Size" and my PC slowed down much. that is not perfect result.

vm-stats here: http://mirik.net.ua/~halic/qb-mem-leeks-v2.jpg
and after closing QB: http://mirik.net.ua/~halic/qb-mem-leeks-v2.2.jpg

2Sveta Smirnova:
вы бы могли и сами догадаться, что нужно что-то делать на протяжении десяти часов, а не просто запусить эту программу.
[14 Oct 2006 10:10] Alexander Holodny 
i can't do "...change the status back...", as you said.
[16 Oct 2006 6:43] Sveta Smirnova 
Thank you for the additional information.

Verified as described.
[2 Aug 2007 23:23] Allen Pike 
It's been a year now - anyone able to look into this? It isn't just that it leaks some memory that gets swapped to disk. Under my usage of 1.2.12, it leaks enough to crash itself fairly often. I can open Activity Monitor on one side and Query Browser on the other, and do a "SELECT 1" repeatedly, watching memory usage balloon by a few MB each time.
[13 Mar 2014 13:35] Omer Barnir 
This bug is not scheduled to be fixed at this time.