decodebin3: push flush-stop event to resume multiqueue's task
Submitted by HoonHee Lee
Link to original bug (#797110)
Description
Dear All.
Deadlock seems to be happened when upstream change(e.g. dynamic stream change) and flush seeking is performed in several times in playbin3(decodebin3).
It means that
- auto plugging is in progress when upstream change
and all parsepads are not exposed from parsebin. - Either flush-start or flush-stop can be failed to travel to sink elements.
Because multiqueue's sinkpad is not linked to parsebin and dropped.
As a result, muitiqueue's task is not resumed without flush-stop
and pipeline seems to be hangup.
Version: 1.14.0