search

ValveSoftware / steam-for-linux

Issue tracking for the Steam for Linux beta client
4.26k stars 175 forks source link

Sporadic Client Crashes #6318

Open CheeseManFuu opened 5 years ago

CheeseManFuu commented 5 years ago

Your system information

Please describe your issue in as much detail as possible:

Probably the biggest disclaimer: As I'm on Manjaro, the keyring only allows me to install a steam-manjaro package, which appears to be a customized build script, so it's possible that it happened specifically because of that. Unfortunately, however, the git is archived and I can't report an issue there, so I'll hope a Dev or a more experienced user can figure this out.

The Steam client randomly shuts down in widely varying time frames (anywhere from once in a day to 3 times within 10 minutes), which immediately shuts down games along with it. I have experimented with launching Steam with STEAM_RUNTIME=0 steam a bit, but shortly went back to running with Runtime as it's the main method of communication for a couple of my friends. As much as a no-no as it is, I have tried completely uninstalling Steam and installing it again. It doesn't appear to be easily manipulated. The only noteworthy things I've noticed recently is closing the main Steam client window only minimizes it now (which is a tad annoying). Other than that, I only have the Friends List up.

EDIT: Fresh crashlogs with the dump file it specifies.

Steps for reproducing this issue:

  1. Open Steam.
  2. Just leave the Steam client open.
  3. Shake my fist and pull my hair in frustration when the Steam client decides to prematurely end my 3 hour Risk of Rain 2 run.
laci200270 commented 5 years ago

Same occours to me. Distro: Solus laci200270_log.txt laci200270_stdout.txt

crash_20190626235614_11.zip

CheeseManFuu commented 5 years ago

Same occours to me. Distro: Solus laci200270_log.txt laci200270_stdout.txt

crash_20190626235614_11.zip

It looks like the problem is sourced from elsewhere between us:

crash_20190603191042_1.dmp[22283]: Uploading dump (out-of-process)
/tmp/dumps/crash_20190603191042_1.dmp
crash_20190603191042_1.dmp[22283]: Finished uploading minidump (out-of-process): success = yes
crash_20190603191042_1.dmp[22283]: response: CrashID=bp-69bd599e-190f-4e03-88c2-27a2e2190603
crash_20190603191042_1.dmp[22283]: file ''/tmp/dumps/crash_20190603191042_1.dmp'', upload yes: ''CrashID=bp-69bd599e-190f-4e03-88c2-27a2e2190603''
/home/cheesemanfuu/.local/share/Steam/steam.sh: line 906: 16127 Segmentation fault      (core dumped) $STEAM_DEBUGGER "$STEAMROOT/$STEAMEXEPATH" "$@"
[0603/203628.920330:ERROR:local_storage_context_mojo.cc(706)] Lost connection to database

vs

crash_20190626235606_6.dmp[18788]: Uploading dump (out-of-process)
/tmp/dumps/crash_20190626235606_6.dmp
crash_20190626234903_1.dmp[18782]: Finished uploading minidump (out-of-process): success = yes
crash_20190626234903_1.dmp[18782]: response: CrashID=bp-5f4e4bf1-1be4-41af-a275-7c8fc2190626
crash_20190626234903_1.dmp[18782]: file ''/tmp/dumps/crash_20190626234903_1.dmp'', upload yes: ''CrashID=bp-5f4e4bf1-1be4-41af-a275-7c8fc2190626''
../common/pipes.cpp (766) : CClientPipe::BWriteAndReadResult: BWaitResult failed, disconnected
../common/pipes.cpp (766) : Fatal assert failed: ../common/pipes.cpp, line 766.  Application exiting.

Looking at the log I also noticed you have STEAM_RUNTIME_HEAVY: ./steam-runtime-heavy, is this a alternative STEAM_RUNTIME variable with more logging? Because if so it may be worth a shot on my end to see if the error changes to yours or something similar to it.

laci200270 commented 5 years ago

i don't know Solus has some native so file overrides for better compatiblilty, but with those tweaks disabled the problem still occours. I don't know when the problem started to happen, about a month ago it was fine, yesterday I've purchased Rocket League on the sale and weren't able to download it at all... Removed ~/.steam and ~/.local/share/steam was able to download then today it bricked itself again My home partition is an ext4 one on LVM and where I store the games is a BTRFS one (it may matter). If there is no relation between the two issues, then sorry but seemed very similar based on the infrequent crashes ( I was able to play rocket leageuz for 5 ours with a few crashes, now can't even play a single round)

laci200270 commented 5 years ago

Okay sorry further searching revaled it might be releated with #6174

laci200270 commented 5 years ago

Okay another crash this time it was running from terminal here is the dump and the last few lines of the log crash_20190627141445_1.zip error.txt This one looks more similar @CheeseManFuu Edit: also how stable is your internet? Just asking because this looks similar to #6219 Edit2: another crashlog laci200270_stdout.txt

laci200270 commented 5 years ago

Update: played an hour in offline mode, no crashes

CheeseManFuu commented 5 years ago

error.txt

Okay, it definitely seems like the same problem now that I see /home/laci200270/.local/share/Steam/steam.sh: 712. sor: 24079 Szegmentálási hiba $STEAM_DEBUGGER "$STEAMROOT/$STEAMEXEPATH" "$@" (Line 712 was the original error, I have no idea why the newer one I have says line 902 since steam.sh has only 724 lines and the binary script only 127, even combined thats 851) Given a small bit of intuition, I assume "Szegmentálási hiba" means Segmentation error, which is spot on for my error.

How stable is your internet?

Better than average. Unless Manjaro massively fucked something up and I never actually noticed. But my average is around 300/50/10ms plugged into ethernet through a double-switch relay, all of which happens maybe less than 40ft/12m away from the router.

Update: played an hour in offline mode, no crashes

An hour is generally how long I last online on average. The other day I actually managed to go a whole day crash-free. But I guess I'll try out running without Runtime sometime this weekend if it's a marked improvement for you.

laci200270 commented 5 years ago

I assume "Szegmentálási hiba" means Segmentation error, which is spot on for my error.

Yeah it means that in Hungarian

How stable is your internet?

Better than average. Unless Manjaro massively fucked something up and I never actually noticed. But my average is around 300/50/10ms plugged into ethernet through a double-switch relay, all of which happens maybe less than 40ft/12m away from the router.

I just asked because the other guy ( @MateusRodCosta ) who is having similar crashes in #6219 was having a similar error message on unreliable wifi networks, and I can't say for sure if my wifi is stable enough

Update: played an hour in offline mode, no crashes

An hour is generally how long I last online on average. The other day I actually managed to go a whole day crash-free. But I guess I'll try out running without Runtime sometime this weekend if it's a marked improvement for you.

Update again: played 3 to 4 hours without crashes offline mode definetly seems to solve the issue. Switching off Solus's native runtime seems to have no difference in the interval of crashes. Also for a lot of cases steam won't live more than 10 minutes before crashing

laci200270 commented 5 years ago

Update again: I've tried running steam with STEAM_RUNTIME=0 steam, but no changes still crashes It seems to crash more frequently when I download anything, but throttling doesn't affect it. My last log ( laci200270_stdout.txt ) has some entries saying libnm (I presume its lib Network Manager) can't read the properties of a device (steam:26505): libnm-glib-WARNING **: 17:09:47.446: async_got_type: could not read properties for /org/freedesktop/NetworkManager/Devices/534: Nincs „org.freedesktop.DBus.Properties” interfész a(z) /org/freedesktop/NetworkManager/Devices/534 útvonalon lévő objektumon , so maybe its releated to NM? Also I've downgraded my kernel to 4.20, no changes

CheeseManFuu commented 5 years ago

Possibly. I've not seen this one, but it's possible. I'm also testing with no Runtime, last night went about 6 hours with nothing, which may have been luck, and I got on my computer not even 10 or 20 minutes ago, so now I play the waiting game.

CheeseManFuu commented 5 years ago

Just went the whole day without Runtime yesterday and no crashing. Possibly luck, so I'll keep this comment updated as I go through more days without Runtime.

Day 2 and no crashes. So I'm inclined to see if it really is something with my Network Manager.

laci200270 commented 5 years ago

Well if its luck I'm pretty unlucky I've tried to play some Don't Starve then this happened: crashLog.txt Here is the relevant dump dump.zip Runtime was disabled, throught it was a bit tricky, needed to call steam.sh directly, it seems Solus has some quirks about how it wants to run Steam

CheeseManFuu commented 5 years ago

Day 3 and I finally got a crash. This log definitely has a lot more information than my previous ones, which is odd since the only difference is Runtime or not, but either way definitely more information.

laci200270 commented 5 years ago

Well, running Steam inside a flatpak image seems to solve the problem, so probably some library issue

CheeseManFuu commented 5 years ago

Decided to do a fresh, vanilla Arch install from scratch..

And it still crashes randomly. Either some package is broken with my hardware or the hardware itself is broken. Will investigate in the next few days.

CheeseManFuu commented 5 years ago

Finally got a GDB log for it with the backtrace, hopefully this has some more information.

Also just in case there is some known hardware issue: CPU: Ryzen 7 1700X at base clock GPU: Gigabyte Radeon RX 580 8GB RAM: GSkill Ripjaw DDR4-2400 (OC 2666) 2x8GB MB: ASRock X370 Killer SSD: Radeon R7 480GB

Edit: After digging with my friend, it's possible the issue may be due to libdbus and be resolved by deleting .local/share/Steam/ubuntu12_32/steam-runtime/pinned_libs_32/ as someone else had the/a similar issue (never told me who/where so thats cool i guess no credit for them), will report over time if this fixes it.

More edit: Nope. Still crashes.

laci200270 commented 5 years ago

Running Steam as FlatPak for a few weeks didn't have any crash today I installed via the package manager just to test it, crashed after half a minute Update did a GDB backtrace aswell:

(gdb) bt
#0  0xf79e1086 in  () at /usr/lib32/libc.so.6
#1  0xe43e8be3 in  () at /home/laci200270/.local/share/Steam/ubuntu12_32/steamclient.so
#2  0xf2ea93c9 in g_cclosure_marshal_VOID__OBJECTv () at /usr/lib32/libgobject-2.0.so.0
#3  0xf2ea651c in  () at /usr/lib32/libgobject-2.0.so.0
#4  0xf2ec342f in g_signal_emit_valist () at /usr/lib32/libgobject-2.0.so.0
#5  0xf2ec3e22 in g_signal_emit_by_name () at /usr/lib32/libgobject-2.0.so.0
#6  0xed251c80 in  () at /usr/lib32/libnm-glib.so.4
#7  0xf1c91ad5 in g_main_context_dispatch () at /usr/lib32/libglib-2.0.so.0
#8  0xf1c91ed9 in  () at /usr/lib32/libglib-2.0.so.0
#9  0xf1c91f84 in g_main_context_iteration () at /usr/lib32/libglib-2.0.so.0
#10 0xef0129ec in  () at /home/laci200270/.local/share/Steam/ubuntu12_32/vgui2_s.so
#11 0xef0224ed in  () at /home/laci200270/.local/share/Steam/ubuntu12_32/vgui2_s.so
#12 0xea3a97e3 in  () at /home/laci200270/.local/share/Steam/ubuntu12_32/steamui.so
#13 0xea3ab456 in  () at /home/laci200270/.local/share/Steam/ubuntu12_32/steamui.so
#14 0xea3ad15e in  () at /home/laci200270/.local/share/Steam/ubuntu12_32/steamui.so
#15 0x5658e1b0 in RunSteam(int, char**, bool) ()
#16 0x5658f0ab in  ()
#17 0x5657a06c in  ()
#18 0xf7961781 in __libc_start_main () at /usr/lib32/libc.so.6
#19 0x5657dd29 in _start ()
(gdb)
CheeseManFuu commented 5 years ago

I started working with the flatpak this weekend and just now got a crash. My luck really is low with Steam, isn't it?

megatog615 commented 5 years ago

I also experience this issue on Debian Testing, so I don't think it's specific to any distro. I get the same segmentation fault from libdbus.

steam[7687]: segfault at 4 ip 00000000ed877543 sp 00000000fff75d10 error 4 in libdbus-1.so.3.5.8[ed857000+48000]

Here's a gdb log.

CheeseManFuu commented 4 years ago

Kind of necroposting this, but I recently left Arch for Debian (god i miss the arch repositories and the AUR with packages that are named decently but oh well), and I will report if I get random crashes still. The random crashing did severely go down towards the end of using Arch, but not 100%.

Also worth noting: Couple of new specs: GPU: Gigabyte Radeon RX 580 8GB SAPPHIRE PULSE RX Vega 56 8GB RAM: GSkill Ripjaw DDR4-2400 (OC 2666) 2x8GB GSkill TridentZ DDR4-3000 (limited to 2666 blegh) 2x8GB SSD: Radeon R7 480GB Samsung 970 EVO Plus NVMe M.2 500GB SSD

magoolachub commented 4 years ago

Bumping, having this same issue. Noticing a trend of everyone reporting this owning an RX 580 GPU, same for me (Sapphire RX 580 Nitro+ Special Edition). Have tested with both native and runtime, no difference, seems to happen more or less depending on game being played (happens quite frequently in dota). Following crash logs are from Arch 5.8.9, xfce desktop, running steam-native, during a game of dota. Other open programs were discord and firefox.

journalctl log

dump files (4)

CheeseManFuu commented 4 years ago

Bumping, having this same issue. Noticing a trend of everyone reporting this owning an RX 580 GPU, same for me (Sapphire RX 580 Nitro+ Special Edition). Have tested with both native and runtime, no difference, seems to happen more or less depending on game being played (happens quite frequently in dota).

It still happened for me as I swapped to the Vega 56 posted above. I feel like your finding for it is just a result of the RX580 being really common because of it being a really great price-point GPU, especially amongst Linux users. Probably has changed since it has been over a year since I opened this thread, so who knows.

Also worth reporting that I don't have much more information from the last ~6 months due to a migration to Windows (which i still have yet to put on my better SSD, woops).

Frontrider commented 3 years ago

This is my exact same problem, in the referenced issue above.

orogenic commented 2 months ago

Arch Linux 6.10.5-arch1-1 steam 1.0.0.81-2 When I clicked "Uninstall" on a game, I got a segfault:

IPC:CSteamEngin[21293]: segfault at 1c8bb241 ip 00000000cb5a2766 sp 00000000c94ed2d4 error 4 in steamclient.so[14bc766,ca218000+19a4000] likely on CPU 11 (core 5, socket 0)