xpra icon
Bug tracker and wiki

#1412 closed defect (needinfo)

High CPU load with Xpra 1.0 on Win 10

Reported by: Lukas Haase Owned by: Lukas Haase
Priority: minor Milestone: 1.0
Component: client Version: 1.0.x
Keywords: Cc:

Description (last modified by Antoine Martin)

I observe high CPU load (100% on one core) when using Xpra 1.0 r14502 on Win 10 doing nothing (no window is being displayed). I just attach to a remote xpra server on Ubuntu.

The high load occurs as soon as it is attached - no matter if windows are displayed or not and it is a specific thread.

In the screenshot attached, the process information can be seen using Process Explorer.

Attachments (2)

high-cpu-load.png (359.9 KB) - added by Lukas Haase 11 months ago.
win10-withsound-nocpu.png (123.3 KB) - added by Antoine Martin 11 months ago.
windows 10 desktop with opus+ogg sound forwarding, using 4% CPU

Download all attachments as: .zip

Change History (6)

Changed 11 months ago by Lukas Haase

Attachment: high-cpu-load.png added

comment:1 Changed 11 months ago by Lukas Haase

A probably useful remark: The issue seems to be the speaker. If I start with speaker=off it works normally.

comment:2 Changed 11 months ago by Antoine Martin

Description: modified (diff)
Owner: changed from Antoine Martin to Lukas Haase

Please see wiki/ReportingBugs and specify: server version and log file, client command output, etc..
In particular the codec that is being used, can you try a different codec?
ie: speaker-codec=mp3

Changed 11 months ago by Antoine Martin

Attachment: win10-withsound-nocpu.png added

windows 10 desktop with opus+ogg sound forwarding, using 4% CPU

comment:3 Changed 11 months ago by Antoine Martin

Priority: majorminor

As you can see here:
windows 10 desktop with opus+ogg sound forwarding, using 4% CPU

A default installation on Windows 10, connected to a Fedora 25 server (running 2.0 beta or 1.0 - no difference), uses opus+ogg for speaker forwarding and uses up about 4% of CPU.

No problem here so lowering priority.

comment:4 Changed 10 months ago by Antoine Martin

Milestone: 1.0
Resolution: needinfo
Status: newclosed

Not heard back, closing.

Note: See TracTickets for help on using tickets.