threadshare: Fix a deadlock in used-socket notification
This manifests in a gst-launch-1.0 pipeline using ts-udpsrc, since notification of used-socket results in the property being read by the application, and the settings lock causes a deadlock.
Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.
This manifests in a gst-launch-1.0 pipeline using ts-udpsrc, since notification of used-socket results in the property being read by the application, and the settings lock causes a deadlock.