Bug #62245 | mysql_stmt_prepare() would lead to memory leaks in libmysqld | ||
---|---|---|---|
Submitted: | 24 Aug 2011 5:20 | Modified: | 20 Feb 2012 18:46 |
Reporter: | Qi Zhou | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: Embedded Library ( libmysqld ) | Severity: | S2 (Serious) |
Version: | 5.5.15, 5.5.22 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | mysql_stmt_prepare mem leaks |
[24 Aug 2011 5:20]
Qi Zhou
[20 Feb 2012 18:46]
Sveta Smirnova
Thank you for the report. Verified as described: ==2590== 2,064 bytes in 1 blocks are definitely lost in loss record 3 of 3 ==2590== at 0x4A05FDE: malloc (vg_replace_malloc.c:236) ==2590== by 0x5462A9: my_malloc (my_malloc.c:38) ==2590== by 0x532974: init_alloc_root (my_alloc.c:63) ==2590== by 0x43AA7F: mysql_stmt_init (libmysql.c:1500) ==2590== by 0x437A43: main (bug62136.cpp:53) To repeat compile test case from bug 62136, then run it as: valgrind --leak-check=full ./bug62136
[20 Feb 2012 18:49]
Sveta Smirnova
Problem is not repeatable without embedded server.