[gstreamer-bugs] [Bug 402562] [gst_parse_launch] Requesting pads but not releasing them

GStreamer (bugzilla.gnome.org) bugzilla-daemon at bugzilla.gnome.org
Thu Aug 28 05:12:52 PDT 2008


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=402562

  GStreamer | gstreamer (core) | Ver: HEAD CVS

Stefan Kost (gstreamer, gtkdoc dev) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|gstreamer-                  |ensonic at sonicpulse.de
                   |bugs at lists.sourceforge.net  |
             Status|UNCONFIRMED                 |ASSIGNED
     Ever Confirmed|0                           |1




------- Comment #5 from Stefan Kost (gstreamer, gtkdoc dev)  2008-08-28 12:12 UTC -------
Created an attachment (id=117520)
 --> (http://bugzilla.gnome.org/attachment.cgi?id=117520&action=view)
release requenstpads when unlinking elements upon removal

Bah, grammar.y uses gst_element_link_pads_filtered() and therefore the use of
requestpads is entierly internal. 

Now I wonder if in theory gstbin.c::unlink_pads() should do cleanup like in the
patch. Te patch has one flaw though. I am afraid it is not safe to release the
request-pad when removing an element from the bin, unless its the request-pad
that belongs to the element being removed. Just imagine having:
tee ! xyz
when app remove xyz, its unlinked, but we can't release the requestpad, as the
app might want to link something to it. Not sure if we could use refcounts of
the request pad.


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




More information about the Gstreamer-bugs mailing list