[gstreamer-bugs] [Bug 580121] New: race condition in GStreamer state changes causes problems in id3v2mux tests

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

  GStreamer | gstreamer (core) | Ver: git
           Summary: race condition in GStreamer state changes causes
                    problems in id3v2mux tests
           Product: GStreamer
           Version: git
          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


I'm not sure if this is a regression or not. I suspect it is, or at least a
pre-existing race exacerbated by the async message handling changes.

It causes problems when a pipeline containing no async elements is set to
playing, and then inserts an async element on the way - such as the test for
id3v2mux, which adds fakesinks to each pad exposed by an id3demux element. 

The fix is really simple, and Wim and I both think it should go in this
release:

http://cgit.freedesktop.org/~thaytan/gstreamer/commit/?h=work&id=c7f8fed3844b7e72cec85c8ee312752193671a80


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