[Bug 674043] New: [0.11] Serialized allocation query deadlocks

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=674043
  GStreamer | gstreamer (core) | 0.11.x

           Summary: [0.11] Serialized allocation query deadlocks
    Classification: Platform
           Product: GStreamer
           Version: 0.11.x
        OS/Version: Mac OS
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: gstreamer (core)
        AssignedTo: gstreamer-bugs at lists.freedesktop.org
        ReportedBy: matej.knopp at gmail.com
         QAContact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---


QT Demuxer deadlocks when posting the (now serialized) allocation query

Stack trace:
#3    0x015c4213 in g_cond_wait ()
#4    0x02d24b1f in gst_multi_queue_sink_query ()
#5    0x01320cb7 in gst_pad_query ()
#6    0x01321697 in gst_pad_peer_query ()
#7    0x0acd25ea in qtdemux_do_allocation ()
#8    0x0acd3313 in gst_qtdemux_add_stream ()
#9    0x0acdeea7 in qtdemux_expose_streams 

gst_multi_queue_sink_query blocks until there is response for the query, but
the response never comes because of a blocking probe. The blocking probe will
be lifted when other streams are exposed, which doesn't happen because qtdemux
loop thread is stuck.

I might be missing something here but how can serialized queries work (given
current implementation) with queues without deadlocking?

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.