Segfault in materialsystem_client.so

[ghost]

Your system information

• System information from steam: https://gist.github.com/light2yellow/d10e31a0e8d4d6ca4430a3e3b6171c1f
• Have you checked for system updates?: Yes

Dec 27 22:00:45.375615 l2y kernel: csgo_linux64[17377]: segfault at 24a ip 00007f79d472a1c1 sp 00007f79ce687e30 error 4 in materialsystem_client.so[7f79d46b6000+16e000]
Dec 27 22:02:52.274276 l2y kernel: ptrace attach of "/home/l2y/.local/share/Steam/steamapps/common/Counter-Strike Global Offensive/csgo_linux64 -steam -freq 60 -console -novid -tickrate 128 -nojoy +exec autoexec.cfg"[17753] was attempted by "gdb -p 17753"[18167]
Dec 27 22:54:37.190024 l2y kernel: csgo_linux64[17765]: segfault at 262 ip 00007f71beca11c1 sp 00007f71b8bfee30 error 4 in materialsystem_client.so[7f71bec2d000+16e000]

As you can see, I tried to attach gdb -p pid but it failed. How can I provide a backtrace?

There are no steam-provided dumps since I am writing this after a reboot (makes sense to not store them in /tmp?). When I reproduce it again, I will add one.

Steps for reproducing this issue:

1. Play one full game at community competitive server (~50 rounds, round ends on team elimination, ~50 minutes of gameplay).
2. Wait until server reloads to map to start a new game.
3. Play 2-5 rounds and get a segfault.

[ghost]

dump.zip It contains crash, assert, _log and _stdout.

The question remains: How can I provide a backtrace?

[kisak-valve]

Hello @light2yellow, assert_20171228221307_1.dmp in your attachment has the backtrace.

[ghost]

@kisak-valve ah, okay. Sorry for the noise.

[ghost]

Some experience-based updates: the issue can be workarounded by a retry just a second or two before the server changes the map - so that the map change happens just as the client attempts to connect. This way no segfaults happen.