[Bug 755400] splitmuxsink: deadlocks when inserted into running pipeline

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=755400

--- Comment #4 from Vincent Penquerc'h <vincent.penquerch at collabora.co.uk> ---
What splitmuxsink does is rather obscure. The hang is due to splitmuxsink
waiting for events such as EOS, flush, and misc more, while in the streaming
thread (in response to the push of a buffer). However, this is the thread that
will be pushing the allocation query that the upstream multiqueue is sending.
I feel like this should be resolved by the wait ending in a "normal" way (ie,
not an EOS nor flush), leading to the buffer push returning, and the
(serialized) allocation query going next. Since taking out the allocation query
makes it work, this implies this is not the case, however.

BTW, the pad block code in the test case needs locking, as it is racy.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.