-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Build 12933 and 12947, crashing GTA5_b3258.exe!sub_1414C81F4 #3173
Comments
I hope this can help, function that crash: |
One thing I have just realised it moved the game build from b3095 to b3258, I thought So both crashes are collision related, is what you think it maybe pointing the problem too? |
Yes, both crashes are collision related, but I don't know the exact cause of the problem. |
How do I go about getting a full dumb? Do I need to do something with WinDbg? |
You can configure FiveM to do full dumps - https://forum.cfx.re/t/enabling-and-uploading-full-client-dumps/1138940 |
We had a similar issue again last night, different crash code but I assume that's because of being on game build 3095 instead of the originally reported 3258
That was caused by someone being malicious and looked to be caused by prop Unless someone else beats me to it, I'll see if I can make my client crash after work, to hopefully confirm the issue. |
Can you share crash dump of that crash?
Confirming that would be a great help. I can't test it for a few hours, so if someone can do it sooner that would be great. |
I have just googled on my phone and found the below, if you then follow the link within that comment, they've got a file called fragment crash, which looks to spawn the object then delete it a second later 🤔 |
What happened?
We moved from b11427 to b12947, to get ourselves more up to date and get the new Node22, but something is causing players within the same area to crash. The problem did move area a few times, but mostly around pillbox probably due to high population area, we do have custom MLO's for Pillbox and Casino. All that we know is something happens and crashes all players in scope or distance from whatever causes the crash, if it's a player causing it we assign the other players have to be within the scope of that player.
We then rolled back to b12933 but the issue still persisted, so we've now just reverted back to b11427 since we can't keep rolling back the build until it doesn't happen because that isn't ideal for the player base.
Multiple of us tried to replicate the issue on our local development instances of fxserver, using the same build and same resources etc, but no joy in being able to recreate the problem.
Crash errors are;
GTA5_b3258.exe!sub_1414C81F4 (0x14) - Seen 952 times
GTA5_b3258.exe!sub_1414C81F4 (0x39) - Seen 370 times
Crashing happened to 400+ users as logged by our logging system
Crash DMP files, hopefully these can aid to what the problem is.
GTA5_b3258.exe!sub_1414C81F4 (0x14) - 8c52c3e5-a966-4397-b283-1e03145292d1.dmp
GTA5_b3258.exe!sub_1414C81F4 (0x39) - 793342b0-f620-442c-9361-458a4c9293f9.dmp
Expected result
No crashing
Reproduction steps
Unable to reproduce sadly.
Importancy
Crash
Area(s)
FiveM
Specific version(s)
FiveM
Additional information
No response
The text was updated successfully, but these errors were encountered: