[gstreamer-bugs] [Bug 548394] New: basesink should ignore EOS during flushing

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=548394

  GStreamer | gstreamer (core) | Ver: HEAD CVS
           Summary: basesink should ignore EOS during flushing
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gstreamer (core)
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: e3423c at motorola.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


When pipeline playback is near the end, basesink is pending on
gst_base_sink_wait_eos. At that time, if users do seek, basesink will received
Flush_start and Flush_stop event, at Flush_start event handler, it will clear
all eos flags and unblock waiting eos. But at gst_base_sink_render_object(),
after it unblocked from bclass->event(), it will still set eos as TRUE, that
will cause pipeline can not work well, even new data coming, it will be
dropped.

So add checking for flushing, if is flushing, ignore this EOS.

Changed files:
gstbasesink.c

Motorola would like to contribute Gstreamer patch to the Gstreamer open source
community project. Please find attached the patch applicable for Gstreamer. For
any questions, please feel free to contact (Zhao Liang "e3423c at motorola.com",
Shi Ling "w20230 at motorola.com").


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=548394.