-
Notifications
You must be signed in to change notification settings - Fork 175
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Steam appears to crash unpredictably when idle #7160
Comments
For reference, assert_20200601162039_1.dmp and crash_20200601165916_2.dmp are SIGFPE in steamclient.so, friendsui.so. The other two are DUMP_REQUESTED in crashhandler.so. |
Interesting. I just tried to grab the latest shell outputs and dumps I had, but I've been trying different methods of launching so they may not line up. Would additional dumps/specific tests be more helpful? Quick edit: I'm not sure if its helpful, but the problem seems significantly less frequent when in-game. For example, yesterday I could barely get Steam to stay up for 5+ minutes, but after starting/playing dota 2 I was able to continue for a couple hours. Steam only crashed once I had exited the game and moved to something else. It has happened during games, but it is far more rare. EDIT: If it's helpful, I was able to capture a crash and its related dumps. This happened while a game was running. Files: |
If this is not the proper channels for it, I apologize, but at this point I'm a little at a loss. I've tried a number of things in an effort to locate the effect, but haven't had any success. Here's a list of things I've tried:
This among a number of small tweaks I've been trying to either source the cause for find a solution. The next thing I'm going to try is running it on just vanilla Ubuntu and if this fails I guess it's got to be hardware, I just can't find what hardware might be causing that, nor do I see any other issues on other platforms or applications. Non-steam games of various variety run fine on linux, even games that don't require Steam running will run fine. It's only the ones that close upon losing Steam that are inaccessible. Without further ado, here's some of the crash info while running DOOM Eternal under plasma/zen/stable src. There are new gdb dumps/logs/stack traces, unfortunately because currently trying to run Steam with GDB gives me the following and I haven't even started to pick this one apart yet:
If any gdb info would be provocatively helpful, I fix that and grab it later. journal/system log
/tmp/gameoverlayui.log
In addition, I've also archived a number of the dumps together and tar'd them: tar I hope that is sufficient information to spark someone's thoughts. Also certainly don't want to come across as demanding an answer, but if anything maybe this info catches someone else with a similar problem or someone who sees a solution that I so clearly cannot! Thanks! |
Hello @dreac0nic, are you still experiencing this issue on an up to date system? |
Closing pending feedback. |
Your system information
Please describe your issue in as much detail as possible:
Steam launches and I can log in just fine. However, any given time while the client is in the background (I have yet to see it crash in front of me), it will suffer a segfault and close. The error messages have largely been unhelpful, and I've attetmpted to dig deeper into them or the minidumps for answers. All I've found is the floating point exception.
Sometimes, I'll be able to play for long periods and have no issues what-so-ever. Steam has even gone all night. Some days I can't even get very far past the Library loading.
Here are some of the dumps and logs from the last few crashes/asserts today:
Tmp log out: gist
Last four minidumps: tar
A couple shell outs from some of the sessions: short, long
Steps for reproducing this issue:
I'm not sure how useful these steps are, but this is all I'm doing.
The text was updated successfully, but these errors were encountered: