diff options
author | Alex Ashley <bugzilla@ashley-family.net> | 2016-04-29 12:31:01 +0100 |
---|---|---|
committer | Tim-Philipp Müller <tim@centricular.com> | 2016-05-06 09:42:41 +0100 |
commit | 792e9a60330d4559e119263400558b5be2f01715 (patch) | |
tree | 156ba3525cc932040361347e83a1af0a20d2ba29 /gst-libs | |
parent | c8e34e93b27f632f0dd227c2b32053ce80b66a33 (diff) | |
download | gstreamer-plugins-bad-792e9a60330d4559e119263400558b5be2f01715.tar.gz |
adaptivedemux: fix threading issues in gst_adaptive_demux_wait_until function
The gst_adaptive_demux_wait_until() function can be woken up either
by its end_time being reached, or from other threads that want to
interrupt the waiting thread.
If the thread is interrupted, it needs to cancel its async clock callback
by unscheduling the clock callback. However, the callback task might already
have been activated, but is waiting for the mutex to become available. In this
case, the call to unschedule does not stop the callback from executing.
The solution to this second issue is to use a reference counted object that
is decremented by both the gst_adaptive_demux_wait_until() function and the
call to gst_clock_id_wait_async (). In this way, the GstAdaptiveDemuxTimer
object is only deleted when both the gst_adaptive_demux_wait_until() function
and the async callback are finished with the object.
https://bugzilla.gnome.org/show_bug.cgi?id=765728
Diffstat (limited to 'gst-libs')
-rw-r--r-- | gst-libs/gst/adaptivedemux/gstadaptivedemux.c | 75 |
1 files changed, 62 insertions, 13 deletions
diff --git a/gst-libs/gst/adaptivedemux/gstadaptivedemux.c b/gst-libs/gst/adaptivedemux/gstadaptivedemux.c index 9c2bb444a..47a7899bb 100644 --- a/gst-libs/gst/adaptivedemux/gstadaptivedemux.c +++ b/gst-libs/gst/adaptivedemux/gstadaptivedemux.c @@ -203,6 +203,7 @@ struct _GstAdaptiveDemuxPrivate typedef struct _GstAdaptiveDemuxTimer { + volatile gint ref_count; GCond *cond; GMutex *mutex; GstClockID clock_id; @@ -285,7 +286,6 @@ gst_adaptive_demux_wait_until (GstClock * clock, GCond * cond, GMutex * mutex, static gboolean gst_adaptive_demux_clock_callback (GstClock * clock, GstClockTime time, GstClockID id, gpointer user_data); - /* we can't use G_DEFINE_ABSTRACT_TYPE because we need the klass in the _init * method to get to the padtemplates */ GType @@ -3501,11 +3501,51 @@ gst_adaptive_demux_get_client_now_utc (GstAdaptiveDemux * demux) return g_date_time_new_from_timeval_utc (>v); } +static GstAdaptiveDemuxTimer * +gst_adaptive_demux_timer_new (GCond * cond, GMutex * mutex) +{ + GstAdaptiveDemuxTimer *timer; + + timer = g_slice_new (GstAdaptiveDemuxTimer); + timer->fired = FALSE; + timer->cond = cond; + timer->mutex = mutex; + timer->ref_count = 1; + return timer; +} + +static GstAdaptiveDemuxTimer * +gst_adaptive_demux_timer_ref (GstAdaptiveDemuxTimer * timer) +{ + g_return_val_if_fail (timer != NULL, NULL); + g_atomic_int_inc (&timer->ref_count); + return timer; +} + +static void +gst_adaptive_demux_timer_unref (GstAdaptiveDemuxTimer * timer) +{ + g_return_if_fail (timer != NULL); + if (g_atomic_int_dec_and_test (&timer->ref_count)) { + g_slice_free (GstAdaptiveDemuxTimer, timer); + } +} + +/* gst_adaptive_demux_wait_until: + * A replacement for g_cond_wait_until that uses the clock rather + * than system time to control the duration of the sleep. Typically + * clock is actually a #GstSystemClock, in which case this function + * behaves exactly like g_cond_wait_until. Inside unit tests, + * the clock is typically a #GstTestClock, which allows tests to run + * in non-realtime. + * This function must be called with mutex held. + */ static gboolean gst_adaptive_demux_wait_until (GstClock * clock, GCond * cond, GMutex * mutex, GstClockTime end_time) { - GstAdaptiveDemuxTimer timer; + GstAdaptiveDemuxTimer *timer; + gboolean fired; GstClockReturn res; if (G_UNLIKELY (!GST_CLOCK_TIME_IS_VALID (end_time))) { @@ -3516,23 +3556,32 @@ gst_adaptive_demux_wait_until (GstClock * clock, GCond * cond, GMutex * mutex, */ return FALSE; } - timer.fired = FALSE; - timer.cond = cond; - timer.mutex = mutex; - timer.clock_id = gst_clock_new_single_shot_id (clock, end_time); + timer = gst_adaptive_demux_timer_new (cond, mutex); + timer->clock_id = gst_clock_new_single_shot_id (clock, end_time); res = - gst_clock_id_wait_async (timer.clock_id, - gst_adaptive_demux_clock_callback, &timer, NULL); + gst_clock_id_wait_async (timer->clock_id, + gst_adaptive_demux_clock_callback, gst_adaptive_demux_timer_ref (timer), + (GDestroyNotify) gst_adaptive_demux_timer_unref); /* clock does not support asynchronously wait. Assert and return */ if (res == GST_CLOCK_UNSUPPORTED) { - gst_clock_id_unref (timer.clock_id); + gst_clock_id_unref (timer->clock_id); + gst_adaptive_demux_timer_unref (timer); g_return_val_if_reached (TRUE); } - /* the gst_adaptive_demux_clock_callback will signal the - cond when the clock's single shot timer fires */ + g_assert (!timer->fired); + /* the gst_adaptive_demux_clock_callback() will signal the + * cond when the clock's single shot timer fires, or the cond will be + * signalled by another thread that wants to cause this wait to finish + * early (e.g. to terminate the waiting thread). + * There is no need for a while loop here, because that logic is + * implemented by the function calling gst_adaptive_demux_wait_until() */ g_cond_wait (cond, mutex); - gst_clock_id_unref (timer.clock_id); - return !timer.fired; + fired = timer->fired; + if (!fired) + gst_clock_id_unschedule (timer->clock_id); + gst_clock_id_unref (timer->clock_id); + gst_adaptive_demux_timer_unref (timer); + return !fired; } static gboolean |