[Bug 763491] typefind: behavior has changed on have-type signal, sets pad caps after signal handlers

[GStreamer (GNOME Bugzilla)]

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

--- Comment #21 from Sebastian Dröge (slomo) <slomo at coaxion.net> ---
First typefind was changed to only set caps after application (aka decodebin)
have-type handlers were called. Then ee44337fc3e3030a5155d28b3561af157e6c6003
in decodebin happened, which would deadlock with the old typefind behaviour.
That is, ee44337fc3e3030a5155d28b3561af157e6c6003 depended on the typefind
change to work correctly.

(Independent of that ee44337fc3e3030a5155d28b3561af157e6c6003 also introduces
lock order problems and other inconsistencies)


No unit test was added obviously ;) It's a crash that happened when running
decodebin in a loop starting and shutting down all the time for a few minutes.

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