GNOME Bugzilla – Bug 660969
qtmux memleak
Last modified: 2011-10-09 14:20:26 UTC
valgrind show the following while muxing with qtmux and moov-recovery-file setted: ==5936== 20,488 bytes in 2 blocks are definitely lost in loss record 5,200 of 5,220 ==5936== at 0x4C28FAC: malloc (vg_replace_malloc.c:236) ==5936== by 0x4C29026: realloc (vg_replace_malloc.c:525) ==5936== by 0x616EB20: g_realloc (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.2800.6) ==5936== by 0x190CFBF5: prop_copy_ensure_buffer (properties.c:53) ==5936== by 0x190CFC3D: copy_func (properties.c:62) ==5936== by 0x190CFCF1: prop_copy_uint32 (properties.c:107) ==5936== by 0x190C72C2: atom_copy_data (atoms.c:1329) ==5936== by 0x190C7D00: atom_ftyp_copy_data (atoms.c:1417) ==5936== by 0x190CDAC1: atoms_recov_write_headers (atomsrecovery.c:116) ==5936== by 0x190C3461: gst_qt_mux_collected (gstqtmux.c:1622) ==5936== by 0x5070AA8: gst_collect_pads_check_collected (gstcollectpads.c:1143) ==5936== by 0x5072977: gst_collect_pads_chain (gstcollectpads.c:1371) ==5936== by 0x52E2DB1: gst_pad_chain_data_unchecked (gstpad.c:4247) ==5936== by 0x52E362A: gst_pad_push_data (gstpad.c:4479) ==5936== by 0x52E642C: gst_pad_push (gstpad.c:4704) ==5936== by 0xBC47864: gst_queue_loop (gstqueue.c:1155) ==5936== by 0x530CBEF: gst_task_func (gsttask.c:318) ==5936== by 0x6191B15: ??? (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.2800.6) ==5936== by 0x618F3E3: ??? (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.2800.6) ==5936== by 0x703AD8B: start_thread (pthread_create.c:304)
commit ca417fd3768cd537cab979212c5e3d33fe63070f Author: Thiago Santos <thiago.sousa.santos@collabora.com> Date: Sun Oct 9 11:18:18 2011 -0300 qtmux: Fix memory leak on atoms recovery function Remember to free the ftyp data after writing it to a file. Fixes #660969