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 699937 - pad: Event mis-orderng caused by "418dcd72 pad: Remove SEGMENT sticky events when flushing"
pad: Event mis-orderng caused by "418dcd72 pad: Remove SEGMENT sticky events ...
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
git master
Other Linux
: Normal normal
: 1.1.1
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-05-08 15:29 UTC by Nicolas Dufresne (ndufresne)
Modified: 2013-05-09 12:14 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Nicolas Dufresne (ndufresne) 2013-05-08 15:29:32 UTC 
This patch will cause sticky even misordering.

commit 418dcd72775f94233351a04433de6763f30bb128
Author: Edward Hervey <edward@collabora.com>
Date:   Sun Nov 11 13:52:25 2012 +0100

    pad: Remove SEGMENT sticky events when flushing
    
    When flushing, it is expected that upstream will send a SEGMENT
    event afterwards.
    This also avoids stray SEGMENT events from coming through after a
    flush.
Comment 1 Sebastian Dröge (slomo) 2013-05-09 12:14:26 UTC 
With this commit and all the other stuff happening over the last days, this should not be a problem anymore... and if it is, something is wrong elsewhere and we get a g_warning().

commit e0f59d22eb414175c2471458c598681210a210cb
Author: Sebastian Dröge <sebastian.droege@collabora.co.uk>
Date:   Thu May 9 10:29:11 2013 +0200

    pad: If we push sticky events because of another sticky event, only push those that come before the new event
    
    https://bugzilla.gnome.org/show_bug.cgi?id=699937