[gstreamer-bugs] [Bug 497002] Decodebin2 deadlock when demuxer bufferallocs on exposed raw pad

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

  GStreamer | gstreamer (core) | Ver: HEAD CVS

Jan Schmidt changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |thaytan at mad.scientist.com




------- Comment #2 from Jan Schmidt  2007-11-15 11:19 UTC -------
You can't check reliably anyway - not atomically.

I think the correct fix will involve having decodebin track pads which come
directly from the demuxer via multiqueue - the should be handled differently to
pads that are buffer-alloc'd through a decoder.

I suppose it is possible to have a buffer-alloc on a decodebin2 output pad from
a decoder which is proxying an upstream buffer-alloc request, but I can't think
of any instances where that is implemented, and I don't know how we would
handle it.


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