Bug #49550 memory leak after filesort
Submitted: 9 Dec 2009 7:37 Modified: 13 Oct 2010 17:18
Reporter: Shane Bester (Platinum Quality Contributor) Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server: DML Severity:S1 (Critical)
Version:5.1.41 OS:Any
Assigned to: CPU Architecture:Any
Tags: Leak, memory leak

[9 Dec 2009 7:37] Shane Bester
Description:
memory leak in 5.1.41:

16,400 bytes in 1 blocks are definitely lost in loss record 7 of 7
at : malloc (in /usr/lib64/valgrind/amd64-linux/vgpreload_memcheck.so)
by : my_malloc (my_malloc.c:34)
by : filesort (filesort.cc:377)
by : create_sort_index (sql_select.cc:13644)
by : JOIN::optimize() (sql_select.cc:1508)
by : subselect_single_select_engine::exec() (item_subselect.cc:1887)
by : Item_subselect::exec() (item_subselect.cc:261)
by : Item_in_subselect::val_bool() (item_subselect.cc:860)
by : Item_in_optimizer::val_int() (item_cmpfunc.cc:1646)
by : Item_func_nop_all::val_int() (item_cmpfunc.cc:354)
by : Item::val_bool() (item.cc:184)
by : Item_cond_and::val_int() (item_cmpfunc.cc:4222)
 
 LEAK SUMMARY:
    definitely lost: 16,400 bytes in 1 blocks.

How to repeat:
no testcase yet. random queries, with multitable update with subqueries.
[23 Mar 2010 9:33] Cyril SCETBON
Hi,

still in 5.1.45 ?
[13 Oct 2010 17:18] MySQL Verification Team
haven't seen this error in a while. can't repeat.