Bug #29687 | mysql_stmt_store_result memory leak in libmysqld | ||
---|---|---|---|
Submitted: | 10 Jul 2007 10:09 | Modified: | 23 Jul 2007 0:47 |
Reporter: | Shane Bester (Platinum Quality Contributor) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Prepared statements | Severity: | S1 (Critical) |
Version: | 5.1.17, 5.1.20 | OS: | Any |
Assigned to: | Alexey Botchkov | CPU Architecture: | Any |
Tags: | memory leak, mysql_stmt_store_result |
[10 Jul 2007 10:09]
Shane Bester
[16 Jul 2007 15:08]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/30968 ChangeSet@1.2527, 2007-07-16 19:08:07+05:00, holyfoot@mysql.com +1 -0 Bug #29687 mysql_stmt_store_result memory leak in libmysqld In embedded server we use result->alloc to store field data for the result, but we didn't clean the result->alloc if the query returned an empty recordset. Cleaning for the empty recordset enabled
[20 Jul 2007 23:46]
Bugs System
Pushed into 5.1.21-beta
[20 Jul 2007 23:49]
Bugs System
Pushed into 5.0.48
[22 Jul 2007 17:58]
Paul DuBois
Noted in 5.0.48, 5.1.21 changelogs. The mysql_stmt_store_result() C API function caused a memory leak for empty result sets.
[22 Jul 2007 18:31]
Sergei Golubchik
in the embedded server - libmysqld - only
[23 Jul 2007 0:47]
Paul DuBois
Updated changelog to note embedded-server only.