[gstreamer-bugs] [Bug 543961] New: Memory leak in gst.Bin.do_handle_message

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=543961

  GStreamer | gst-python | Ver: HEAD CVS
           Summary: Memory leak in gst.Bin.do_handle_message
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-python
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: mutex at runbox.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


Please describe the problem:
Overloading do_handle_message cause a memory leak on message (and associated
structure).

Steps to reproduce:
1. launch the attached python file


Actual results:
a launch under valgrind cause the following output :
==12618== 5,960 bytes in 116 blocks are possibly lost in loss record 34 of 48
==12618==    at 0x4022765: malloc (vg_replace_malloc.c:149)
==12618==    by 0x4708AF5: g_malloc (in /usr/lib/libglib-2.0.so.0.1400.1)
==12618==    by 0x471D50A: g_slice_alloc (in /usr/lib/libglib-2.0.so.0.1400.1)
==12618==    by 0x471DBE4: g_slice_alloc0 (in /usr/lib/libglib-2.0.so.0.1400.1)
==12618==    by 0x4591536: g_type_create_instance (in
/usr/lib/libgobject-2.0.so.0.1400.1)
==12618==    by 0x44F6424: gst_mini_object_new (gstminiobject.c:181)
==12618==    by 0x44F54B9: gst_message_new_custom (gstmessage.c:278)
==12618==    by 0x44F571B: gst_message_new_element (gstmessage.c:690)
==12618==    by 0x4A43210: gst_udpsrc_create (gstudpsrc.c:449)
==12618==    by 0x44A64F4: gst_push_src_create (gstpushsrc.c:117)
==12618==    by 0x4498930: gst_base_src_get_range (gstbasesrc.c:1779)
==12618==    by 0x449C430: gst_base_src_loop (gstbasesrc.c:1985)
==12618== 
==12618== 
==12618== 7,793,891 (1,180,840 direct, 6,613,051 indirect) bytes in 59,042
blocks are definitely lost in loss record 44 of 48
==12618==    at 0x4021AA4: calloc (vg_replace_malloc.c:279)
==12618==    by 0x4708A5D: g_malloc0 (in /usr/lib/libglib-2.0.so.0.1400.1)
==12618==    by 0x45100BA: gst_structure_id_empty_new_with_size
(gststructure.c:116)
==12618==    by 0x45106B5: gst_structure_new_valist (gststructure.c:238)
==12618==    by 0x4510731: gst_structure_new (gststructure.c:209)
==12618==    by 0x4A43201: gst_udpsrc_create (gstudpsrc.c:449)
==12618==    by 0x44A64F4: gst_push_src_create (gstpushsrc.c:117)
==12618==    by 0x4498930: gst_base_src_get_range (gstbasesrc.c:1779)
==12618==    by 0x449C430: gst_base_src_loop (gstbasesrc.c:1985)
==12618==    by 0x4516815: gst_task_func (gsttask.c:192)
==12618==    by 0x47260C7: (within /usr/lib/libglib-2.0.so.0.1400.1)
==12618==    by 0x47245AE: (within /usr/lib/libglib-2.0.so.0.1400.1)
==12618== 
==12618== 
==12618== 2,866,068 (1,302,960 direct, 1,563,108 indirect) bytes in 21,716
blocks are definitely lost in loss record 47 of 48
==12618==    at 0x4022765: malloc (vg_replace_malloc.c:149)
==12618==    by 0x4708AF5: g_malloc (in /usr/lib/libglib-2.0.so.0.1400.1)
==12618==    by 0x471D50A: g_slice_alloc (in /usr/lib/libglib-2.0.so.0.1400.1)
==12618==    by 0x471DBE4: g_slice_alloc0 (in /usr/lib/libglib-2.0.so.0.1400.1)
==12618==    by 0x4591536: g_type_create_instance (in
/usr/lib/libgobject-2.0.so.0.1400.1)
==12618==    by 0x44F6424: gst_mini_object_new (gstminiobject.c:181)
==12618==    by 0x44F54B9: gst_message_new_custom (gstmessage.c:278)
==12618==    by 0x44F571B: gst_message_new_element (gstmessage.c:690)
==12618==    by 0x4A43210: gst_udpsrc_create (gstudpsrc.c:449)
==12618==    by 0x44A64F4: gst_push_src_create (gstpushsrc.c:117)
==12618==    by 0x4498930: gst_base_src_get_range (gstbasesrc.c:1779)
==12618==    by 0x449C430: gst_base_src_loop (gstbasesrc.c:1985)

Expected results:


Does this happen every time?


Other information:


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=543961.