I've found the exact cause of this problem.
The CVRPipewireAppManager::PipewireThread() function in vrserver is constantly spinning and eating CPU cycles. Binary patching the function to instead return gets rid of the increased CPU use.
Thanks for the report. Can you send the output of pw-dump when in the bad state?
Ie. pw-dump &> dump.json and send the dump.json. Thanks!
Great find! The screen mirror in SteamVR stays black for me, sometimes I can still move the cursor. I also experienced problems with wayvr screen mirroring when using Steam VR. That is also using pipewire with GNOME. Maybe this is related https://github.com/wlx-team/wayvr/issues/270
@baracoder steamvr can not capture the desktop on Wayland. For it you have to use x11. Or use wayvr. You could try using the x11 Wayland video bridge, but there is a chance of it being VERY unreliable. Steamvr desktop capture is already hit or miss on x11
@misyltoad
here's dump.json from my system, while observing ~100% CPU usage from vrserver
Are folks still seeing this on the 2.16.5 beta?
@Packetdancer im not seeing this exact issue ever since the beta but vrserver now no longer dies after you disconnect the headset or press Exit VR
@PhialsBasement - That's a separate issue, #876 -- I've already tracked down and fixed that one in main (so hopefully it'll make it into the next beta build)
@Packetdancer Very cool! Thank you for the bugfixes!
Closing per the last handful of comments.
Nothing extracted yet.
Describe the bug
vrserveruses 100% of a CPU core, even without any headset connected. CPU usage is much lower with WiVRn.If other users don't observe this, it could be related to my dual GPU setup: Radeon 880M onboard and Radeon RX 9070 XT eGPU. Or it could be related to the virtual screen as it stays black. Using GNOME.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
System Information (please complete the following information):
Please use the latest Steam beta client and SteamVR beta for your bug reports!
Additional context
Add any other context about the problem here.