[gstreamer-bugs] [Bug 462558] New: Regression in async state change handling

[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=462558

  GStreamer | gstreamer (core) | Ver: HEAD CVS
           Summary: Regression in async state change handling
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: blocker
          Priority: Normal
         Component: gstreamer (core)
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: thaytan at mad.scientist.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


Attempting to play a musepack file in playbin no longer succeeds in pre-rolling
with the current 0.10.13.4 pre-release.

The problem seems to be caused by the state-change changes since 0.10.13,
specifically the handling of async-start/async-done messages.

Attaching some munged gst debug logs that show the sequence. The problem seems
to be that the fakesink which decodebin uses to trigger an async state change
sends an async-start message, and is then removed before decodebin actually
finishes changing state. When it is removed, it sends an async-done, which is
not forwarded by decodebin because it has not yet finished changing state,
despite the fact that decodebin did originally send an async-start to the
parent when it received the original async-start from its child fakesink.

The end result is that playbin thinks decodebin is still changing state
asynchronously when it has in fact already completed.


-- 
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=462558.