[Bug 767666] splitmuxsink: infinite change_state loop

[GStreamer (GNOME Bugzilla)]

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

--- Comment #8 from Xavier Claessens <xclaesse at gmail.com> ---
(In reply to Jan Schmidt from comment #5)
> I don't understand your bug description. How can you have an infinite
> looping state change function and not see any outward signs. You'd think
> it'd crash or use 100% CPU or something.

State transition is made from another thread, it is gst_bin_continue_func()
that runs in loop, if I understand correctly. So that's not preventing the rest
of the pipeline to work.

This clearly needs a test case, I'll try to find time to write one.

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