[gstreamer-bugs] [Bug 612406] New: Race condition in rtspsrc

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=612406
  GStreamer | gst-plugins-good | 0.10.16

           Summary: Race condition in rtspsrc
    Classification: Desktop
           Product: GStreamer
           Version: 0.10.16
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-good
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: anders.skargren at axis.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
      GNOME target: ---
     GNOME version: ---


Created an attachment (id=155720)
 --> (https://bugzilla.gnome.org/attachment.cgi?id=155720)
gstreamer log showing the race condition and abort.

There is a race condition in rtspsrc in conjunction with using the timeout
property and changing the state of the element to NULL.

Attaching a gstreamer log showing an abort cause by this.
In this log the rtspsrc is set to receive data over multicast with a timeout of
10 seconds. Due to a router on the way not letting the multicast traffic pass
it times out (timestamp 0:00:31.145568704).

Hence the rtspsrc begins shutting down.

Very soone afterwards, our controlling application who has set up a similar
timeout of 10 seconds times out and gets scheduled before the rtspsrc is
done(at 0:00:31.196563630). It then sets the pipeline to NULL in the call to
media_streamer_disconnect_nolock().

This seems to trigger a parallel state change on rtspsrc and confuses it
completely, ending with the Gstreamer-CRITICAL.

rtspsrc doesnt seem MT safe...

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.