Bug #50993 | mem-leak if MySQL pre-4.1 client connects to MySQL Proxy | ||
---|---|---|---|
Submitted: | 8 Feb 2010 13:26 | Modified: | 20 Apr 2010 16:05 |
Reporter: | Jan Kneschke | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Proxy: Core | Severity: | S3 (Non-critical) |
Version: | 0.7.x, 0.8.0 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[8 Feb 2010 13:26]
Jan Kneschke
[9 Feb 2010 8:40]
Sveta Smirnova
Thank you for the report. I can not repeat described behavior using valgrind-3.5.0. Which additional circumstances should I use?
[10 Mar 2010 0:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[30 Mar 2010 16:18]
Enterprise Tools JIRA Robot
Kay Roepke writes: fixed on launchpad (also released in 0.8): Revision ID: jan@mysql.com-20100208112310-xuhr3423clpc3ntp fixed mem-leak on 4.0 clients connect
[20 Apr 2010 16:05]
MC Brown
A note has been added to the 0.8.0 changelog: A memory leak could occur in MySQL Proxy if MySQL v4.0 or earlier clients connected to the proxy.