[gstreamer-bugs] [Bug 572577] New: [playbin2] deadlock on shutdown
GStreamer (bugzilla.gnome.org)
bugzilla-daemon at bugzilla.gnome.org
Fri Feb 20 09:10:44 PST 2009
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=572577
GStreamer | gst-plugins-base | Ver: git
Summary: [playbin2] deadlock on shutdown
Product: GStreamer
Version: git
Platform: Other
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: gst-plugins-base
AssignedTo: gstreamer-bugs at lists.sourceforge.net
ReportedBy: manauw at skynet.be
QAContact: gstreamer-bugs at lists.sourceforge.net
GNOME version: Unspecified
GNOME milestone: Unspecified
Consider a playbin2 pipeline that is set to PAUSED, and (about) immediately
upon return from set_state set to READY, then a race occurs between the
(mainloop) thread trying to shutdown to READY, and streaming thread callbacks
building the bin and prerolling to PAUSED.
In particular, with an internal decodebin2 not yet linked to downstream
elements, mainloop may choose to move decodebin2 elements to READY first, and
then tries to acquire STREAM_LOCK as part of pad deactivation.
In the meantime, streaming thread may then link decodebin2 to downstream
elements, resume streaming and waiting prerolled for a state change.
A state change will not come as the mainloop is occupied trying to get the
STREAM_LOCK, which it will not get as streaming is stuck PAUSED.
--
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=572577.
More information about the Gstreamer-bugs
mailing list