Is this related to this bug? https://github.com/ValveSoftware/steam-for-linux/issues/5493#issuecomment-564765268
Seems to be definitely related. @TTimo , traces in the bug report may help you?
I can confirm that
mv ~/.steam/ubuntu12_32/steam-runtime/amd64/usr/bin/steam-runtime-system-info ~/.steam/ubuntu12_32/steam-runtime/amd64/usr/bin/steam-runtime-system-info.backup
is a workaround for this issue too.
@Emanem: steam-runtime-system-info is executed at startup and should exit after 10 to 30 seconds typically.
Can you check if that process hangs on your system? If it's still there after a minute or two, see this comment and provide a trace?
If srt-info isn't well behaved and hangs, that shouldn't be causing particular problems for the Steam client, so I'll look at that anyway. Thanks for the traces.
Is this still happening in latest beta client? (>= 2019-12-19 version)
More specifically, is this happening at startup, without going to Help > System Information to trigger steam-runtime-system-info process.
Unless you can reproduce in those conditions, this is likely a duplicate of https://github.com/ValveSoftware/steam-for-linux/issues/5493
@TTimo @kisak-valve Will test as soon as I can, I would tend to agree with you that most likely is a duplicate of #5493
The new steam client build (>= 19-12-2019) seems to have fixed it. Closing this issue.
System Info
Please describe your issue in as much detail as possible:
After 1 minute running, the steam client uses 100% CPU until closing it down.
I can clearly see from htop that the CPU time is 60% user and 40% system.
That's why I've attached a strace of the steam process.
Please find also a strace at startup, when the CPU is only used around 10% or less.
At the end of this trace the infinite loop starts.
Looking at the traces, seems like when it goes into an infinite loop there are calls to futex and other OS APIs which are not present in the sane strace:
Steps for reproducing this issue: