After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 777522 - parsebin: Clear drained mark with FLUSH_STOP
parsebin: Clear drained mark with FLUSH_STOP
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
git master
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-01-20 06:47 UTC by Seungha Yang
Modified: 2018-11-03 11:53 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
parsebin: Clear drained mark with FLUSH_STOP (3.24 KB, patch)
2017-01-20 06:48 UTC, Seungha Yang 		none Details | Review
parsebin: Clear drained mark with FLUSH_STOP (3.24 KB, patch)
2017-01-20 06:57 UTC, Seungha Yang 		none Details | Review

Description Seungha Yang 2017-01-20 06:47:31 UTC 
A demuxer might re-expose source pads during playback
(e.g., program update in tsdemux).
When pads are re-exposed, EOS event will be pushed to the old source
pads by demuxer, and group switching is triggered by the EOS event.
Note that the EOS will mark "drained" to chain/group and
parsebin refers to the "drained" marks for chain/group switching.

However, since the "drained" marks never be cleared once it was set,
following sequence cannot be handled
  * demuxer pushed EOS and parsebin marked the chain/group as drained
  * seek event happened
  * demuxer source pads are re-exposed

To handle above case, "drained" marks should be cleared by flush-stop
Comment 1 Seungha Yang 2017-01-20 06:48:49 UTC 
Created attachment 343863 [details] [review]
parsebin: Clear drained mark with FLUSH_STOP
Comment 2 Seungha Yang 2017-01-20 06:57:16 UTC 
Created attachment 343864 [details] [review]
parsebin: Clear drained mark with FLUSH_STOP
Comment 3 GStreamer system administrator 2018-11-03 11:53:54 UTC 
-- 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/330.