rtspsrc deadlocking

[Joona Laine]

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?

Anyone got any ideas?




--
View this message in context: http://gstreamer-devel.966125.n4.nabble.com/rtspsrc-deadlocking-tp4678879.html
Sent from the GStreamer-devel mailing list archive at Nabble.com.