[Bug 767666] splitmuxsink: infinite change_state loop

[GStreamer (GNOME Bugzilla)]

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

--- Comment #9 from Jan Schmidt <thaytan at noraisin.net> ---
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.

For now, I've reverted the commit which switched from using some internal logic
to using the bin's async-handling.

commit 5a71334fb0be6f1bd4c15815c7dad3567306d47b
Author: Jan Schmidt <jan at centricular.com>
Date:   Mon Aug 8 02:53:48 2016 +1000

    Revert "splitmuxsink: Use GstBin async-handling instead of our own."

    This reverts commit fa008f271a52f82dededc28bd81b020ca7939b47.

    async-handling in GstBin causes the pipeline to spin at 100%
    CPU as the top-level pipeline tries to change that state
    to PLAYING constantly. This is a workaround for a core
    problem, essentially, but an improvement in this case for now.

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