[gstreamer-bugs] [Bug 608179] New: caps filter appearing after adder results in deadlock
GStreamer (bugzilla.gnome.org)
bugzilla at gnome.org
Tue Jan 26 10:06:30 PST 2010
https://bugzilla.gnome.org/show_bug.cgi?id=608179
GStreamer | gstreamer (core) | 0.10.25
Summary: caps filter appearing after adder results in deadlock
Classification: Desktop
Product: GStreamer
Version: 0.10.25
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: gstreamer (core)
AssignedTo: gstreamer-bugs at lists.sourceforge.net
ReportedBy: rob at yorba.org
QAContact: gstreamer-bugs at lists.sourceforge.net
CC: adam at yorba.org
GNOME target: ---
GNOME version: ---
Executing the following pipeline with gst-launch results in a deadlock about
one in five times on my system. Placing the caps filter after audioresample
avoids this problem.
In one thread (the ui thread), update_degree is locking the capsfilter and then
the adder. In another thread (gst_capsfilter_transform_caps near the top of
the call stack), gst_adder_sink_get_caps locks the adder and then tries to lock
the caps filter in gst_capsfilter_transform_caps.
gst-launch adder name=mix ! capsfilter
caps=audio/x-raw-int,rate=48000,channels=2,width=16,depth=16 ! gconfaudiosink \
filesrc location=junk.wav ! wavparse ! audioconvert ! audioresample ! mix. \
filesrc location=junk.wav ! wavparse ! audioconvert ! audioresample ! mix. \
filesrc location=junk.wav ! wavparse ! audioconvert ! audioresample ! mix. \
filesrc location=junk.wav ! wavparse ! audioconvert ! audioresample ! mix. \
filesrc location=junk.wav ! wavparse ! audioconvert ! audioresample ! mix. \
filesrc location=junk.wav ! wavparse ! audioconvert ! audioresample ! mix. \
filesrc location=junk.wav ! wavparse ! audioconvert ! audioresample ! mix. \
filesrc location=junk.wav ! wavparse ! audioconvert ! audioresample ! mix. \
filesrc location=junk.wav ! wavparse ! audioconvert ! audioresample ! mix.
--
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.
More information about the Gstreamer-bugs
mailing list