-
Notifications
You must be signed in to change notification settings - Fork 71
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
Segfault before CS:GO logo after The Danger Zone update #1901
Comments
Hello @echoz28, if you find any CrashIDs or minidumps (commonly found in |
Here's the minidump: And here is the output from ./csgo.sh: |
For reference, the attached minidump is a SIGSEGV in engine_client.so. |
If it's any use this is the output of: |
Can you take a look at #1801 and see if it is relevant to your system? (low confidence guess) |
I didn't have the |
I had time now to try a reinstall of the game, and it worked. Not sure what caused the problem to happen in the first place, but I've had this installation for some years now, so I suppose it needed to be cleaned out. Tried one round of Danger Zone, and everything seems to work fine. I even won 1st place. |
Your system information
Steam
->Help
->System Information
) in a gist: https://gist.github.com/echoz28/77f0660eb6779249ec5c555f52810786Please describe your issue in as much detail as possible:
Describe what you expected should happen and what did happen. Please link any large pastes as a Github Gist.
Expected: Game launches and I'm able to play
Reality: Game crashes right before it would normally show the CS:GO logo:
[1024918.938985] csgo_linux64[3918]: segfault at 58 ip 00007f3e209d258b sp 00007ffd11b72920 error 4 in libSDL2-2.0.so.0[7f3e2091b000+f8000]
[1024919.094827] csgo_linux64[3858]: segfault at 0 ip 00007f3e19954b0d sp 00007ffd11b73190 error 6 in engine_client.so[7f3e19436000+b33000]
The game has been working up until this point. The last issue I had was November 15 when I had to replace filesystem_stdio_client.so, but this has since been fixed, and the file has been updated to the new version. This also affected all users, which this clearly does not.
Tried: Verify game files, -nojoy
Steps for reproducing this issue:
The text was updated successfully, but these errors were encountered: