[Bug 755169] dashdemux: can we have multiple seek events at the same time?

GStreamer (GNOME Bugzilla) bugzilla at gnome.org
Wed Sep 23 08:06:01 PDT 2015


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

--- Comment #36 from Vincent Penquerc'h <vincent.penquerch at collabora.co.uk> ---
(In reply to Florin Apostol from comment #34)
> (In reply to Vincent Penquerc'h from comment #32)
> Traditionally gstreamer accesses to an object are protected by taking that
> object lock, so I propose to not confuse other readers and use the same
> approach in adaptivedemux: use the demux object lock. So I propose you start

This unfortunately runs into a problem, as the object lock is taken by various
other code, outwith adaptivedemux, leading to deadlocks when, eg, posting a
message (the object lock is taken by gst_element_post_message_default).

Thus, we either need to keep using the manifest lock here, or temporarily
unlock the object lock.

This also explains why there's a temp unlock where you said:
> Personally I don't see why we should unlock. So what if it post messages on the bus?

It would not be necessary to unlock if we were using the manifest lock (as I
don't think any recursive calls into adaptivedemux by way of messages are
expected).

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


More information about the gstreamer-bugs mailing list