MySQL Bugs: #5049: Query Browser has mem-leaks

Bug #5049	Query Browser has mem-leaks
Submitted:	14 Aug 2004 0:01	Modified:	16 Feb 2005 11:25
Reporter:	Jorge del Conde	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Query Browser	Severity:	S1 (Critical)
Version:	1.0.5	OS:	Windows (Win32)
Assigned to:	Mike Lischke	CPU Architecture:	Any

Description:
Query Browser is full of memory leaks!

How to repeat:
Run Query Browser through a mem-leak checker such as Purify, QA Sleuth, Dev Partner, and even the way suggested by MS using standard system tools.

The output of these tools depends on how many things you do in QA.

For these results, I only executed 2 queries:

Memory leaks:10
Resource leaks:32
Failures:0 
Modules loaded:61 
Modules analyzed:1   //This means only Query Browser was analyzed .. none of the DLL's where tested during this test.
Debug messages:0

I closed some critical and a large number of non-critical mem-leaks (memory that was allocated once and freed by the OS automatically on program termination) but there are some leaks which I do not understand - seem to be reported incorrect or caused by underlaying system components. Could you run the test once again and analyze one callstack on the code based on the current code in the repository and point me to the actual mem-leak? Thanks in advance.

I still get a lot of memory leaks with the latest release.

There is no sense in analyzing the callstack unless you provide us with a full DEBUG instrumented release.

Can you please put up for download a full DEBUG release ?

I added a Purify report file

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

After fixing a few remaining things I ran several Memproof sessions with QB and found only one bogus leak message. Including the system DLLs into the test showed a lot more problems, but these are not directly related to QB. So I'm closing this bug for now until someone proves fixable leaks.