[Bug 767666] splitmuxsink: infinite change_state loop

[GStreamer (GNOME Bugzilla)]

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

--- Comment #11 from Xavier Claessens <xclaesse at gmail.com> ---
(In reply to Jan Schmidt from comment #9)
> This seems to be a fundamental problem in core with bins that have
> async-handling=TRUE because they don't send async-start, but return ASYNC
> from the state change function. The pipeline just tries to continue state
> constantly because it has no async-start message stored from the child.

So that should happen with other elements than splitmuxsink? That sounds more
blocker than ever, no?

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