[Bug 684312] rtspsrc: mutex blocks going to NULL state

[GStreamer (bugzilla.gnome.org)]

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

Wim Taymans <wim.taymans> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |wim.taymans at gmail.com
         Resolution|                            |FIXED
   Target Milestone|HEAD                        |1.0.3

--- Comment #11 from Wim Taymans <wim.taymans at gmail.com> 2012-12-10 14:19:01 UTC ---
commit 3503aef946649da39e9b423adebe173f7a692b89
Author: Aleix Conchillo Flaque <aleix at oblong.com>
Date:   Thu Sep 27 12:17:58 2012 -0700

    rtspsrc: do not change state to PLAYING if currently chaning state

    * gst/rtsp/gstrtspsrc.c (gst_rtspsrc_play): state change might be
      happening in the application thread, so we don't change the state to
      PLAYING in the gstrtspsrc thread unless it is safe.

      A specific case is when chaning the state to NULL from the application
      thread. This will synchronously try to stop the task (with the element
      state lock acquired), but we will try a gst_element_set_state from
      gstrtspsrc thread which will block on the element state lock causing a
      deadlock.

      https://bugzilla.gnome.org/show_bug.cgi?id=684312

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