Open Singustromo opened 1 month ago
I found out by surprise that the steamwebhelper
continuously writes crash dumps to /tmp/dumps/completed
up to a point where it fills up the /tmp
mounted partition
lsof +r2 | grep completed
steamwebh 10864 user 3r DIR 0,43 152520 102 /tmp/dumps/completed
steamwebh 10864 10865 steamwebh user 3r DIR 0,43 152520 102 /tmp/dumps/completed
steamwebh 10864 10866 steamwebh user 3r DIR 0,43 152520 102 /tmp/dumps/completed
Here are some of those crash dumps: https://0x0.st/XgqT.7z/steamwebhelper_crashdumps_11305.7z
Having similar issue and it turns out it's because steamwebhelper is crashing. I posted my bug submission.
Are you still experiencing this issue @Singustromo? I've just run into this issue and I'm also on Void with an AMD GPU, it ran perfectly fine before today and I have tried reinstalling steam and all its dependencies and purging local files with no luck.
Your system information
Please describe your issue in as much detail as possible:
The steam client has been working under Void as expected for years. Recentely it just stopped opening the main window. I haven't changed my hardware, maybe a specific package update was the cause. The processes are still running and a thread of the steamwebhelper is at 100%. I left it running for ~30 minutes just to make sure it's not an unlogged update without a finding.
This also happens when I don't "sandbox" the home directory via environment variables. I've also tried to delete
$HOME/.steam*
and$HOME/.local/share/steam/*
with the exception of thesteamapps
directory and reinstalled steam. After that, the client grabs the bootstrap files of around 400MB and would then behave as explained above.Steps for reproducing this issue:
I am just executing Steam.