[Bug 763491] Typefind behavior has changed on have-type signal
GStreamer (GNOME Bugzilla)
bugzilla at gnome.org
Sat Mar 12 11:00:14 UTC 2016
https://bugzilla.gnome.org/show_bug.cgi?id=763491
Sebastian Dröge (slomo) <slomo at coaxion.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
--- Comment #8 from Sebastian Dröge (slomo) <slomo at coaxion.net> ---
commit a15fca193485ef8f9ae71fd44b8f794ba4132588
Author: Sebastian Dröge <sebastian at centricular.com>
Date: Sat Mar 12 12:56:28 2016 +0200
Revert "typefind: Store caps on the pad before emitting have-type but send
it downstream only in the default signal handler"
This reverts commit 0835c3d6569dde0ec9e5524436367c7678cc4a4a.
It causes deadlocks in decodebin, which currently would deadlock if the
caps
are already on the pad in have-type and are forwarded while copying the
sticky
events (while holding the decodebin lock)... as that might cause the next
element to expose pads, which then calls back into decodebin and takes the
decodebin lock.
This needs some more thoughts.
--
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