[gstreamer-bugs] [Bug 497002] New: 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
           Summary: Decodebin2 deadlock when demuxer bufferallocs on exposed
                    raw pad
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gstreamer (core)
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: ext-tommi.myohanen at nokia.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


I have a case where 

 * demuxer exposes (first) raw pad inside decodebin2
 * decodebin2 plugs multiqueue to the raw pad
 * decodebin2 exposes multiqueue src pad and sets it blocked
 * demuxer prepares to push first buffer and calls gst_pad_alloc_buffer
 * multiqueue bufferalloc function is called
 -> deadlock, bufferalloc blocks because multiqueue src pad is blocked and
demuxer can't go on

Should the first buffers be allocated by multiqueue in case the src pad is
blocked?


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