[Bug 759535] gst_clock_id_unschedule isnt thread safe

[GStreamer (GNOME Bugzilla)]

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

Sebastian Dröge (slomo) <slomo at coaxion.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |slomo at coaxion.net

--- Comment #1 from Sebastian Dröge (slomo) <slomo at coaxion.net> ---
That's correct and probably not possible to fix. What can happen is e.g. that
gst_system_clock_async_thread() is just calling your callback, then
unschedule() is called and there is no way to stop your callback from being
called anymore.

What is threadsafe about this API however is that you can call all functions
from any thread at any time. It's not guaranteed though that no thread is
inside your callback somewhere after unschedule() is called.

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