[Bug 760757] gstsystemclock: incorrect handling of wait requests

[GStreamer (GNOME Bugzilla)]

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #9 from Sebastian Dröge (slomo) <slomo at coaxion.net> ---
commit e10a220a63b4eaa9f2c131da8f8161fb66dbe74a
Author: Florin Apostol <florin.apostol at oregan.net>
Date:   Mon Jan 18 22:45:58 2016 +0000

    systemclock: tests: added stress test for async order

    Keep inserting alarms at the beginning of the list. Due to
    https://bugzilla.gnome.org/show_bug.cgi?id=760757
    alarm thread will get confused and not serve them in order.

commit 4e2250e531df41f9795d1f6879e78110dcac9a6a
Author: Florin Apostol <florin.apostol at oregan.net>
Date:   Mon Jan 18 16:25:20 2016 +0000

    systemclock: fixed race condition in handling alarms

    When choosing the first entry from the list, gst_system_clock_async_thread
    must set the entry state to busy before releasing the clock lock. Otherwise
    a new entry could be added to the beginning of the list and
    gst_system_clock_async_thread will be unaware and keep waiting on the entry
    it has already chosen.

    Also improved messages about expected state and bumped them to ERROR level
    to detect unexpected state changes.

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

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