[Bug 773681] directsoundsink: High cpu usage on windows x86

[GStreamer (GNOME Bugzilla)]

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

--- Comment #32 from Sebastian Dröge (slomo) <slomo at coaxion.net> ---
commit 2d44b53ff664658ba9a4578b5b3231365c7c8e71
Author: Nirbheek Chauhan <nirbheek at centricular.com>
Date:   Wed May 3 23:23:10 2017 +0530

    directsoundsink: Fix corner case causing large CPU usage

    We were unnecessarily looping/goto-ing repeatedly when we had exactly
    the amount of data as the free space, and also when the free space was
    too small. This, as it turns out, is a very common scenario with
    Directsound on Windows.

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

    We have to do polling here because the event notification API that
    Directsound exposes cannot be used with live playback since all events
    must be registered in advance with the capture buffer, you cannot
    add/remove them once playback has begun. Directsoundsrc had the same
    problem.

    See also: https://bugzilla.gnome.org/show_bug.cgi?id=781249

commit 0700b1f0b0dd6b986f232c993b20929cee69ed6a
Author: Nirbheek Chauhan <nirbheek at centricular.com>
Date:   Wed May 3 23:31:00 2017 +0530

    directsoundsink: Clean up some debug logging

    Don't need to print the function name, gstreamer does it for you.

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

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