Announcement

Collapse
No announcement yet.

Steam will hang using 100% CPU, keeping new applications from launching, and requiring a hard reset.

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Steam will hang using 100% CPU, keeping new applications from launching, and requiring a hard reset.

    When using the native version of Steam, it will suddenly experience some sort of crash. This might be while downloading something or just selecting something in a menu. Steam will become mostly unresponsive, but will allow some navigation of the UI. The rest of my desktop works, but only things that were open before the crash. New applications won't start including terminal windows. I usually have a terminal window already running anyway and running htop shows a number of steam processes some of them in either Z or D state. One of them in R state will be using 100% CPU. I've tried every process killing method I could find and nothing other than a hard reset works.

    I did my best to wipe my steam install and switched to the flatpak version but after setting the overrides to point to the other drives I have Steam libraries on (like the C drive for my windows install) Steam would just get confused and put new empty steam libraries in those folders and not look at the right ones. I tinkered with it a bit just putting my entire media folder with all drives as an override (maybe stupid idk) and shortly after I got the same unkillable crash. I wiped the flatpak install and I'm back on the native version and still getting the crash.

    Running steam through the terminal, it prints this twice when the crash happens:
    Code:
    src/clientdll/steamengine.cpp (2868) : Assertion Failed: CSteamEngine::BMainLoop appears to have stalled > 15 seconds without event signalled​
    My specs are:
    Desktop: KDE Plasma v: 5.27.12
    Distro: Kubuntu 24.04.2 LTS (Noble Numbat)
    Mobo: Gigabyte X570 AORUS ELITE
    CPU: AMD Ryzen 7 3700X
    GPU: AMD Radeon RX 5700




Working...
X