xpra icon
Bug tracker and wiki

This bug tracker and wiki are being discontinued
please use https://github.com/Xpra-org/xpra instead.

Opened 20 months ago

Last modified 16 months ago

#2905 new defect

xpra shadow server dies and drives 400% CPU

Reported by: stdedos Owned by: stdedos
Priority: major Milestone: 4.2
Component: server Version: 3.0.x
Keywords: Cc:


Server v3.0.12-r27620 started with:

"Xpra-Python3-x86_64_4.1-r27676\xpra_cmd" shadow ssh://user@ip/0 --ssh="plink -ssh -agent" -d ssh --env=XPRA_SHADOW_REFRESH_DELAY=200 --title="@title@ on @@/@server-display@" --opengl=no --bandwidth-limit=6Mbps --desktop-scaling=0.75 --webcam=no --speaker=off --microphone=off --pulseaudio=no

args=--ssh="plink -ssh -agent" -d ssh --env=XPRA_SHADOW_REFRESH_DELAY=200 --title="@title@ on @@/@server-display@" --opengl=no --bandwidth-limit=6Mbps --desktop-scaling=0.75 --webcam=no --speaker=off --microphone=off --pulseaudio=no

2020-10-16 13:25:23,032 parse_ssh_string(plink -ssh -agent)
2020-10-16 13:25:24,148 Xpra GTK3 client version 4.1-r27676 64-bit
2020-10-16 13:25:24,153  running on Microsoft Windows 10
2020-10-16 13:25:25,612 GStreamer version 1.18.0 for Python 3.8.6 64-bit
2020-10-16 13:25:26,174 created named pipe 'Xpra\5392'
2020-10-16 13:25:26,514 keyboard layout code 0x409
2020-10-16 13:25:26,514 identified as 'United States - English' : us
2020-10-16 13:25:26,643 executing ssh command: "plink" "-ssh" "-agent" "-l" "sntentos" "-T" "" "sh -c 'if [ -x $XDG_RUNTIME_DIR/xpra/run-xpra ]; then $XDG_RUNTIME_DIR/xpra/run-xpra _proxy_shadow_start ":0" "--opengl=no" "--title=@title@ on @@/@server-display@" "--bandwidth-limit=6Mbps" "--ssh=plink -ssh -agent" "--desktop-scaling=0.75" "--debug=ssh" "--speaker=off" "--env=XPRA_SHADOW_REFRESH_DELAY=200";elif which "xpra" > /dev/null 2>&1; then xpra _proxy_shadow_start ":0" "--opengl=no" "--title=@title@ on @@/@server-display@" "--bandwidth-limit=6Mbps" "--ssh=plink -ssh -agent" "--desktop-scaling=0.75" "--debug=ssh" "--speaker=off" "--env=XPRA_SHADOW_REFRESH_DELAY=200";elif [ -x /usr/local/bin/xpra ]; then /usr/local/bin/xpra _proxy_shadow_start ":0" "--opengl=no" "--title=@title@ on @@/@server-display@" "--bandwidth-limit=6Mbps" "--ssh=plink -ssh -agent" "--desktop-scaling=0.75" "--debug=ssh" "--speaker=off" "--env=XPRA_SHADOW_REFRESH_DELAY=200";elif [ -x ~/.xpra/run-xpra ]; then ~/.xpra/run-xpra _proxy_shadow_start ":0" "--opengl=no" "--title=@title@ on @@/@server-display@" "--bandwidth-limit=6Mbps" "--ssh=plink -ssh -agent" "--desktop-scaling=0.75" "--debug=ssh" "--speaker=off" "--env=XPRA_SHADOW_REFRESH_DELAY=200";elif [ -x Xpra_cmd.exe ]; then Xpra_cmd.exe _proxy_shadow_start ":0" "--opengl=no" "--title=@title@ on @@/@server-display@" "--bandwidth-limit=6Mbps" "--ssh=plink -ssh -agent" "--desktop-scaling=0.75" "--debug=ssh" "--speaker=off" "--env=XPRA_SHADOW_REFRESH_DELAY=200";else echo "no run-xpra command found"; exit 1; fi'"
2020-10-16 13:25:26,719 Warning: libqrencode not found
2020-10-16 13:25:26,905  keyboard settings: layout=us
2020-10-16 13:25:26,916  desktop size is 4160x1440 with 1 screen:
2020-10-16 13:25:26,918   Default (1100x381 mm - DPI: 96x96) workarea: 4160x1400
2020-10-16 13:25:26,920     Generic PnP Monitor 1600x900 at 0x534 (309x174 mm - DPI: 131x131) workarea: 1600x860 at 0x534
2020-10-16 13:25:26,921     C32JG5x 2560x1440 at 1600x0 (697x392 mm - DPI: 93x93) workarea: 2560x1400 at 1600x0
2020-10-16 13:25:26,921  downscaled to 75%, virtual screen size: 5547x1920
2020-10-16 13:25:26,922   Default (1100x381 mm - DPI: 128x128) workarea: 5547x1867
2020-10-16 13:25:26,923     Generic PnP Monitor 2133x1200 at 0x712 (309x174 mm - DPI: 175x175) workarea: 2133x1147 at 0x712
2020-10-16 13:25:26,924     C32JG5x 3413x1920 at 2133x0 (697x392 mm - DPI: 124x124) workarea: 3413x1867 at 2133x0

And it was connected, and left idle. After some time, I assume it died (lost the client log), and it drove both itself (and a vmware-virtual box (!!)) both to 400% CPU.

Server gave the #2904 when it was asked to give xpra-info.

Find attached "new" xpra-info and the display.log

Attachments (2)

redact-xpra-info-server-ABSURD-CPU.log (37.0 KB) - added by stdedos 20 months ago.
redact-xpra-info-server.log (22.4 KB) - added by stdedos 20 months ago.

Download all attachments as: .zip

Change History (7)

Changed 20 months ago by stdedos

Changed 20 months ago by stdedos

Attachment: redact-xpra-info-server.log added

comment:1 Changed 17 months ago by Antoine Martin

Owner: changed from Antoine Martin to stdedos

If you can reproduce this, please enable full debug:

xpra control $DISPLAY debug enable all

And post the server log. It must be doing something..

comment:2 Changed 17 months ago by stdedos

Accurately for every start :-p

I guess I can start it (from client) with xpra shadow ssh:// --debug=all?
Of course, I still need to install the new v3 and test it before anything ...

comment:3 Changed 17 months ago by Antoine Martin

I guess I can start it (from client) with xpra shadow ssh:// --debug=all?


Last edited 17 months ago by Antoine Martin (previous) (diff)

comment:4 Changed 17 months ago by Antoine Martin

Milestone: 4.14.2

comment:5 Changed 16 months ago by migration script

this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/2905

Note: See TracTickets for help on using tickets.