[pulseaudio-tickets] [Bug 80772] New: Windows XP: PulseAudio consumes too much CPU when launched with high priority

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=80772

          Priority: medium
            Bug ID: 80772
                CC: lennart at poettering.net
          Assignee: pulseaudio-bugs at lists.freedesktop.org
           Summary: Windows XP: PulseAudio consumes too much CPU when
                    launched with high priority
        QA Contact: pulseaudio-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: Windows (All)
          Reporter: mikedep333 at gmail.com
          Hardware: x86 (IA32)
            Status: NEW
           Version: unspecified
         Component: misc
           Product: PulseAudio

Created attachment 102099
  --> https://bugs.freedesktop.org/attachment.cgi?id=102099&action=edit
PulseAudio log while this bug is reproduced on XP SP3 32-bit

As reported in the X2Go bugtracker (bug #526 by "Nable 80"):
http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=526

When I use sound forwarding and launch inside X2Go session some application
with sound support, pulseaudio.exe at client side starts consuming ~100% CPU.
By default, X2Go Client starts pulseaudio.exe with high priority (13).
When I set priority to "Above Normal (10)" PA's CPU load drops to 10-20%.
With "Normal (8)" it drops to almost 0%, although sound is still played stable,
without any additional delays.

I'm using WinXP SP3 (32-bit) on my laptop with single core CPU.
This issue seems to be "PulseAudio 5.0 && WinXP"-specific.

--------

As I mentioned in a follow-up, I was able to reproduce this issue on a VM.
("setup #2")  Therefore, I assume it affects all Windows XP machines. The VM
was dual-core and only 1 CPU core was being maxed out by PulseAudio. 

I also assume it affects windows server 2003 and server 2003 R2 due to their
similarity with Windows XP. Those 2 server OS's are supported by Microsoft
through July 2015.

For now, we on the X2Go project plan to work around this bug by lowering the
priority of PulseAudio, but only when we are running on Windows XP or server
2003 (R2). We ship & use PulseAudio 5.0 on Windows.

I ran into another bug ("setup #1") (I cloned it as bug #530), but I think that
an OS misconfiguration that was at fault. So just ignore that in this bug
report.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/pulseaudio-bugs/attachments/20140701/6a44b02f/attachment.html>