[gstreamer-bugs] [Bug 568289] gst_pad_template_new() leaks caps it's supposed to take ownership of

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

  GStreamer | gstreamer (core) | Ver: 0.10.x

Tim-Philipp Müller changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
            Summary|memoryleaks when running    |gst_pad_template_new() leaks
                   |example code (and all others|caps it's supposed to take
                   |as well).                   |ownership of




------- Comment #4 from Tim-Philipp Müller  2009-01-19 16:21 UTC -------
> It still does not solve the errors I get from valgrind.
> How could this not be a bug (there are more): ?

I don't think I ever claimed that GStreamer is free of leaks or bugs :)

> 27,134 (888 direct, 26,246 indirect) bytes in 6 blocks are definitely lost in
> ..
> gst_caps_new_empty (in
> /usr/lib/libgstreamer-0.10.so.0.18.0)
> gst_riff_create_audio_template_caps
> (riff-media.c:1566)
> gst_ogm_audio_parse_base_init (gstogmparse.c:290)

You are right, there is a leak here. We do know about this issue though, and it
will probably be fixed in CVS quite soon (the reason it wasn't fixed
immediately is that there were other modules which used certain API
incorrectly, so those had to be fixed and released first).

See this remark in gstpadtemplate.c, gst_pad_template_new():

#if 0
  /* FIXME: enable this after gst-ffmpeg-0.10.6 and
   * gst-plugins-good-0.10.11 have been released.  Previous versions
   * depend on broken core behavior. */
  if (caps)
    gst_caps_unref (caps);
#endif

Feel free to file bugs about any other leaks you find (would be best to test
with CVS of all modules).


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