[Bug 761586] systemclock: regression causing audiomixer to stall
GStreamer (GNOME Bugzilla)
bugzilla at gnome.org
Wed Feb 10 13:02:37 UTC 2016
https://bugzilla.gnome.org/show_bug.cgi?id=761586
Thiago Sousa Santos <thiagossantos at gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Target Milestone|git master |1.7.2
--- Comment #9 from Thiago Sousa Santos <thiagossantos at gmail.com> ---
Thanks for spotting the missing piece of the patch and, specially, for the
tests!
commit 2b0ff13d070f370286078c5531b2e13006e5ce98
Author: Stian Selnes <stian at pexip.com>
Date: Wed Feb 10 09:09:29 2016 +0100
systemclock: Fix wait/unschedule race
Fixes a race where an entry is set to BUSY in
gst_system_clock_id_wait_jitter() and is UNSCHEDULED before
gst_system_clock_id_wait_jitter_unlocked() starts processing it. The
wakeup added by gst_system_clock_id_unschedule() must be cleaned up.
Two stress tests are added. One test that triggers the specific issue
described above. The second stresses the code path where a wait is
rescheduled because the poll returned early.
https://bugzilla.gnome.org/show_bug.cgi?id=761586
commit 77a98d98cbed15e0bfdd8fe982b7ac83b1826d13
Author: Thiago Santos <thiagoss at osg.samsung.com>
Date: Fri Feb 5 15:34:47 2016 -0300
systemclock: handle unschedule of late entries
If the clockentry is too late and is unscheduled before it gets
a change to detect its lateness the wakeup count and the poll are
used but never properly cleaned up. This leaves it in a dirty state
that is going to mess with the next clock entry waiting requests.
https://bugzilla.gnome.org/show_bug.cgi?id=761586
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
More information about the gstreamer-bugs
mailing list