GNOME Bugzilla – Bug 797110
decodebin3: push flush-stop event to resume multiqueue's task
Last modified: 2018-11-03 12:10:15 UTC
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 1) auto plugging is in progress when upstream change and all parsepads are not exposed from parsebin. 2) 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.
Created attachment 373581 [details] [review] decodebin3: push missed flush-stop to resume multiqueue's task
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gst-plugins-base/issues/486.