Open darix opened 2 days ago
Can confirm the findings of that thread on KDE Tumbleweed Wayland.
It started happening around the time "record your game" rolled out for me.
Valve should fix all the preload errors that spam the console when using it and playing games
Pulling this from a reddit topic I saw where the user also had the issue, may be relevant:
"When I run 'top' in the terminal I see the game running 'engMain', when I have it focused, the %CPU will show somewhere between 300 - 400 when not moving my mouse - the game runs fine. When I touch my mouse the %CPU value plummets to about half of whatever was initially shown and the game stutters. This does not happen when the game is initially started"
I'm the one who started this recently in the other repo issues and I can confirm that it is still happening. You can get rid of this by using LD_PRELOAD=""
, but you can still use LD_PRELOAD
to preload your own libraries.
Can confirm the findings of that thread on KDE Tumbleweed Wayland.
It started happening around the time "record your game" rolled out for me.
Exactly.
Also happens to me on gnome 47, Wayland, fedora 41, Nvidia 560 and 565, started happening when the game recording update came out. Additionally I'm not sure if it's part of the same problem but with the overlay enabled doing nothing (no game recording enabled, no windows, no chat, nothing) the overlay vram usage balloons to almost 2gb reported by nvidia-smi.
@kisak-valve I just want to add that this also happens when the overlay is turned off through the Steam UI.
(with also both game recording and steam input disabled as well, from the UI of course)
https://github.com/doitsujin/dxvk/issues/4436#issuecomment-2466438353
Having the same problem, started after the Steam Game Recording update as well, enabling the overlay fixed the problem.
I've had this issue for years https://github.com/ValveSoftware/csgo-osx-linux/issues/2901 but I only play 1-2 games, so after CS:GO moved to CS2, the issue went away.
But for years, CS:GO using DXVK native required LD_PRELOAD=""
gameoverlayrenderer.so most likely culprit
gameoverlayrenderer.so most likely culprit
It definitely is.
But many of us have the steam overlay and recording feature turned off in the options. So why would it even load that?
But many of us have the steam overlay and recording feature turned off in the options. So why would it even load that?
That's probably part of the bug. /environ shows that the library still loads even though those things are turned off. Hence why LD_PRELOAD=""
fixes the issue (prevents said library from loading).
A lot of details are already collected in:
https://github.com/doitsujin/dxvk/issues/4436
it could be related for a LD_PRELOAD added for the "record your game" feature?
the workaround while we wait for the fix
please see this comment for all the details https://github.com/doitsujin/dxvk/issues/4436#issuecomment-2466646597