[gstreamer-bugs] [Bug 474880] New: [xvimagesink] [ximagesink] leaking buffer caps reference

[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=474880

  GStreamer | gst-plugins-base | Ver: HEAD CVS
           Summary: [xvimagesink] [ximagesink] leaking buffer caps reference
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: minor
          Priority: Normal
         Component: gst-plugins-base
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: mail at renestadler.de
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


Yesterday, Stefan said on IRC that he found a leaked caps using valgrind in
conjunction with xvimagesink usage.

I found out that ximagesink is also affected.  I tracked the problem down to
the fact that the custom GstBuffer subclasses that these elements use do not
chain up to the parent class' "finalize" vmethod.  This results in buffer->caps
and buffer->malloc_data never being freed on buffer object destruction.

Attaching patches.


-- 
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=474880.