Steam and Proton Game crash when client tries to run a gpu-trace command

steamopen Steam clientDistro Family: ArchProton

ValveSoftware/steam-for-linux#7985 · opened 2021-08-12 by thyTwilightGoth · updated 2021-12-08 · 7 comments · github

TthyTwilightGoth 2021-08-12 github

Your system information

Steam client version: 1628721164
Distribution: Arch Linux (Kernel: 5.13.9-xanmod1-1(AMD 17h patch applied))
Opted into Steam client beta?: Yes
Have you checked for system updates?: Yes

Please describe your issue in as much detail as possible:

As far as I know this only effects games ran via proton. The expected behavior is the game and steam continue to run as normal, however eventually the steam client tries to execute a gpu-trace command and that command fails crashing both the game and steam. This also happens to effect the base 5.13.9 kernel and non-beta client.

https://gist.github.com/thyTwilightGoth/4f768d7cb0eb4fff06ff40888e327115

Steps for reproducing this issue:

Unknown at this point.

Eemma-the-rock 2021-08-12 github

i'm having the same problem, do you have an NVIDIA gpu too?

TthyTwilightGoth 2021-08-12 github

i'm having the same problem, do you have an NVIDIA gpu too?

I have a AMD GPU.

Bbpc1 2021-08-21 github

Same here steam client crashes with error "failed to run command: gpu-trace --get-tracing-status". It seems quite random, was as short as few minutes to multiple hours of playing. The game works fine after the crash only the steam client crashes for me.

OS: Manjaro Linux
KERNEL: 5.10.56-1-MANJARO
CPU: AMD Ryzen 5 3600 6-Core
GPU: NVIDIA NVIDIA GeForce RTX 2060
GPU DRIVER: NVIDIA 470.57.02

Edit: Just to remove one more variable the reason my game i tried still runs after steam crash is because it was gta 5 and it launches rockstar launcher so it doesn't need steam to still run after crash. Also my crash log is basically identical to the other peoples posted here so don't see the point posting mine.

Nnickistre 2021-08-23 github

I'm seeing something very similar with this environment:

Steam client version: 1626824053
Distribution: Manjaro Linux
Opted into Steam client beta?: No
Have you checked for system updates?: Yes

KERNEL: 5.12.19-1-MANJARO x86_64 (Also happens on 5.13 kernel)
CPU: AMD Ryzen 5 5600X
GPU: AMD Radeon RX 6900 XT
GPU Driver: amdgpu

Vulkan Driver Info:
    driverID           = DRIVER_ID_MESA_RADV
    driverName         = radv
    driverInfo         = Mesa 21.1.6 (ACO)
    conformanceVersion = 1.2.3.0

My crash log looks very similar to OP's: https://gist.github.com/nickistre/b9922e2b182ed2816468cfb23f821235#file-gistfile1-txt

Symptoms are basically the game I'm playing would freeze, and I could tab out to find that Steam has closed or crashed. I'm guessing the DRM check would find steam not running, so the game process would just halt. I have to kill the game process and restart steam, then start the game again. Sometimes I can play for hours without this happening, or sometimes it happens within minutes. It's rather frustrating to play any games that require Steam to be running at this point.

Bbpc1 2021-08-23 github

After some more testing i figured out it was mangohud causing the crashes. The constant " >>> Adding process _ for game ID _ " spam was caused by it. So just disable mangohud until whatever is causing the issue is fixed.

Nnickistre 2021-08-23 github

After some more testing i figured out it was mangohud causing the crashes. The constant " >>> Adding process _ for game ID _ " spam was caused by it. So just disable mangohud until whatever is causing the issue is fixed.

Might be something to this. I just completely uninstalled MangoHUD from my system, and I did just play through 1.5 hours of gaming without Steam crashing. I'll continue playing this afternoon and tonight, then reinstall and re-activate MangoHud later to see if it happens again, then put up a crash report there.

Kkokoko3k 2021-12-08 github

The issue seems still present, is there a workaround to continue to use mangohud?

Nothing extracted yet.