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: | |
Category: | MySQL Query Browser | Severity: | S1 (Critical) |
Version: | 1.0.5 | OS: | Windows (Win32) |
Assigned to: | Mike Lischke | CPU Architecture: | Any |
[14 Aug 2004 0:01]
Jorge del Conde
[19 Aug 2004 14:31]
Michael G. Zinner
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.
[12 Sep 2004 20:48]
Jorge del Conde
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 ?
[2 Oct 2004 23:31]
MySQL Verification Team
I added a Purify report file
[16 Feb 2005 11:25]
Mike Lischke
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.