rtspsrc deadlocking

[Sebastian Dröge]

On Do, 2016-07-28 at 00:36 -0700, Joona Laine wrote:
> This signal is called from the streaming thread, you should therefore not do
> any state changes on rtspsrc because this might *deadlock*. If you want to
> modify the state as a result of this signal, post a
> GST_MESSAGE_REQUEST_STATE message on the bus or signal the main thread in
> some other way.
> 
> This reads on the rtspsrc signal-details on "handle-request" (also found
> here
> https://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-plugins-good-plugins/html/gst-plugins-good-plugins-rtspsrc.html#GstRTSPSrc-handle-request)
> 
> When I'm setting my pipeline to NULL state I get warnings about PAUSE and
> TEARDOWN interruptions. Could the above be the reason?

What exactly are you doing? Maybe provide a runnable testcase to
reproduce your problem.

Also a backtrace of all threads when it hangs might be useful, as well
as the version of GStreamer and the plugins you're using.

-- 
Sebastian Dröge, Centricular Ltd · http://www.centricular.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 949 bytes
Desc: This is a digitally signed message part
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20160729/d0e08168/attachment.sig>