Hi Nable, sorry to hear you are running into this bug.
On Jun 29, 2014 7:52 AM, "Nable 80" <nable.maininbox@googlemail.com> wrote:
Included version of PulseAudion consumes too much CPU with default
settings.
I've observed such behaviour on my laptop with single core CPU and WinXP SP3 x86.
- Does this happen on 4.0.2.0? Both versions use PulseAudio 5.0. They even use the same exact build of PulseAudio.
- On 4.0.2.0 at least, I've observed this bug on my VM with the same OS. I assumed it was a compatibility bug with the virtual hardware (fedora 20 KVM, I'll check what sound adapter model).
It looks like pulseaudio.exe uses some polling: (stacktrace from Process Explorer) ntdll.dll!KiFastSystemCallRet USER32.dll!GetLastInputInfo+0x105 USER32.dll!MsgWaitForMultipleObjects+0x1f libpulsecommon-5.0.dll!pa_poll+0x2f7 libpulse-0.dll!pa_mainloop_poll+0x185 pulseaudio.exe+0x13de kernel32.dll!RegisterWaitForInputIdle+0x49
I'm not familiar much with polling.
and frequency depends on priority of process. By default pulseaudio.exe is started with high priority (13, I don't know whether this setting is set by PA or X2Go Client) and it leads to ~100% CPU load. 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 assuming our x2goclient code sets that priority. Id probably be ok with setting it to normal priority instead. I'll probably look into this matter today or tomorrow.
Could you please report this as a bug? http://wiki.x2go.org/doku.php/wiki:bugs
Mike1#, I'd like this to block 4.0.2.1. Especially because my this bug interferes with XP users using their computer, the computer becomes very unresponsive.
-Mike#2 Windows maintainer for X2Go Client