[Bug 700342] decodebin: Crashes and deadlocks when setting to READY while still autoplugging

GStreamer (bugzilla.gnome.org) bugzilla at gnome.org
Wed May 22 10:20:59 PDT 2013


https://bugzilla.gnome.org/show_bug.cgi?id=700342
  GStreamer | gst-plugins-base | 1.0.7

--- Comment #14 from Sebastian Dröge <slomo at circular-chaos.org> 2013-05-22 17:20:51 UTC ---
Ok, what I said above really can't happen. When the decode chains are freed,
the state change function already chained up to the GstBin and GstElement state
change function. This would've stopped all dataflow while holding the pad's
stream locks.

Now our callbacks are called from inside the data flow and thus these stream
locks are hold. So the callbacks should've returned already before the GstBin
and GstElement state change functions returned and before we free the decode
chain.

That's for gdb-log-3.


For gdb-log-4, the above is exactly happening. The GstBin and GstElement state
change functions are shutting down all data flow and are holding the pad's
stream lock for that... unfortunately some multiqueue is holding the stream
lock still and waiting forever for an allocation query to be answered.

-- 
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