adaptivedemux: release the manifest lock ...
authorMathieu Duponchelle <mathieu.duponchelle@opencreed.com>
Wed, 31 May 2017 00:46:01 +0000 (02:46 +0200)
committerEdward Hervey <bilboed@bilboed.com>
Mon, 12 Jun 2017 14:10:26 +0000 (16:10 +0200)
before broadcasting preroll.

The deadlock was as follows:

-> The subclass pushes a buffer on a newly-created stream in T1
-> We take the preroll lock in T1, to handle_preroll
-> The demuxer is stopped in T2, we take the MANIFEST_LOCK
-> T1 starts blocking because it received a reconfigure event
   and needs to take the MANIFEST_LOCK
-> T2 deadlocks because it now wants the preroll_lock.

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

gst-libs/gst/adaptivedemux/gstadaptivedemux.c

index 4f80eb6..392e1e1 100644 (file)
@@ -1974,9 +1974,11 @@ gst_adaptive_demux_stop_tasks (GstAdaptiveDemux * demux, gboolean stop_updates)
     g_mutex_unlock (&stream->fragment_download_lock);
   }
 
+  GST_MANIFEST_UNLOCK (demux);
   g_mutex_lock (&demux->priv->preroll_lock);
   g_cond_broadcast (&demux->priv->preroll_cond);
   g_mutex_unlock (&demux->priv->preroll_lock);
+  GST_MANIFEST_LOCK (demux);
 
   g_mutex_lock (&demux->priv->manifest_update_lock);
   g_cond_broadcast (&demux->priv->manifest_cond);