[Bug 754212] New: cutter: Fix buffer leak

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=754212

            Bug ID: 754212
           Summary: cutter: Fix buffer leak
    Classification: Platform
           Product: GStreamer
           Version: git master
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: gst-plugins-good
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: vineeth.tm at samsung.com
        QA Contact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---

Buffer is added to the internal cache, and pushed only when accumulated buffer
duration crosses 200 ms. So when the chain ends, the buffer accumulated is not
freed. Adding a finalize method to free the cache.

leak with the below pipeline
audiotestsrc num-buffers=200 ! cutter threshold=1 ! fakesink

==27003== 18,424 (12 direct, 18,412 indirect) bytes in 1 blocks are definitely
lost in loss record 3,577 of 3,579
==27003==    at 0x402C17C: malloc (in
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
==27003==    by 0x43D1BE2: g_malloc (in
/lib/i386-linux-gnu/libglib-2.0.so.0.4002.0)
==27003==    by 0x43E8281: g_slice_alloc (in
/lib/i386-linux-gnu/libglib-2.0.so.0.4002.0)
==27003==    by 0x43C83E0: g_list_append (in
/lib/i386-linux-gnu/libglib-2.0.so.0.4002.0)
==27003==    by 0x404817E: gst_cutter_chain (gstcutter.c:370)
==27003==    by 0x41F0BC7: gst_validate_pad_monitor_chain_func
(gst-validate-pad-monitor.c:2039)
==27003==    by 0x427EC7D: gst_pad_push_data (gstpad.c:4085)
==27003==    by 0x4874A5A: gst_base_src_loop (gstbasesrc.c:2845)
==27003==    by 0x42B3138: gst_task_func (gsttask.c:331)
==27003==    by 0x42B41EE: default_func (gsttaskpool.c:68)
==27003==    by 0x43F3404: ??? (in /lib/i386-linux-gnu/libglib-2.0.so.0.4002.0)
==27003==    by 0x43F29A9: ??? (in /lib/i386-linux-gnu/libglib-2.0.so.0.4002.0)
==27003==    by 0x4498F6F: start_thread (pthread_create.c:312)
==27003==    by 0x4599BED: clone (clone.S:129)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.