Closed tmpaajsdlkjasld closed 4 weeks ago
I also experience the same pattern. No matter whether launching in normal or legacy OpenGL mode.
Arch Linux 6.9.0-rc4-next-20240419
AMD Radeon RX 6700 XT (RADV NAVI22)
Mesa 24.1.0-devel (git-04f232ed99)
Dmesg output.
[11805.104124] [ T47206] tf_linux64[47206]: segfault at 7fffd032b370 ip 00007fffcef0196f sp 00007fffffffc160 error 4 in client.so[7fffce7b6000+e31000] likely on CPU 11 (core 5, socket 0)
[11805.104133] [ T47206] Code: 2d ee 60 25 01 85 d2 49 8b 4d 00 0f 84 d2 01 00 00 83 fa ff 0f b7 c2 be ff 1f 00 00 48 0f 44 c6 c1 ea 10 48 c1 e0 05 48 01 c8 <39> 50 10 0f 85 b0 01 00 00 48 83 78 08 00 0f 84 a5 01 00 00 48 8b
@tmpaajsdlkjasld Can you add the Steam CrashID to the post? Should also be in the journal when the game crashes
@Nocrex for some reason no crashid is present in the journal even when I reproduce the crash...
@tmpaajsdlkjasld try launching steam from a terminal and see if it shows up there
@Nocrex ok I've reproduced and it gives CrashID=bp-79172d40-4aec-441a-9a38-ddd812240421
This seems to be fixed by the latest update :)
This issue seems to be back. After updating and successfully playing a few matches and restarting the game it was as if the update was reverted.
[ 4331.278221] [ T78225] tf_linux64[78225]: segfault at 7fffba72b370 ip 00007fffb9301649 sp 00007fffffffbb90 error 4 in client.so[7fffb8bb6000+e31000] likely on CPU 9 (core 3, socket 0)
CrashID=bp-6197ac00-5393-439e-bc7d-e55a62240423
@ThGrSoRu so it was fixed and you re-encountered it?
@ThGrSoRu so it was fixed and you re-encountered it?
Yes.
I just tested again and it did not crash this time. It seems to be more inconsistent now.
Restarted again and crashed again.
For me this also happens, but not always. On Fedora Linux 40.
System Info:
Reproduce: Launch tf2 join a server then pick a character it will spawn you and instantly crash
journalctl
This stack trace is the same as https://github.com/ValveSoftware/Source-1-Games/issues/5653 starting at their 4th line except the client.so address/offset is different
I strongly suspect it's the same issue but I'm not 100% sure apologies if it is a dupe