[Bug 759535] gst_clock_id_unschedule isnt thread safe

[GStreamer (GNOME Bugzilla)]

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

--- Comment #6 from Sebastian Dröge (slomo) <slomo at coaxion.net> ---
That's why the GDestroyNotify parameter of gst_clock_id_wait_async() exists.
You somehow need to ensure that the user_data is going to be valid until the
callback was called or the clock id is destroyed.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.