Skip to content
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

Open
FingerlessGlov3s opened this issue Feb 19, 2025 · 8 comments · May be fixed by #3182
Open

Build 12933 and 12947, crashing GTA5_b3258.exe!sub_1414C81F4 #3173

FingerlessGlov3s opened this issue Feb 19, 2025 · 8 comments · May be fixed by #3182
Assignees
Labels
bug crash triage Needs a preliminary assessment to determine the urgency and required action

Comments

@FingerlessGlov3s
Copy link

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

@FingerlessGlov3s FingerlessGlov3s added bug triage Needs a preliminary assessment to determine the urgency and required action labels Feb 19, 2025
@github-actions github-actions bot added the crash label Feb 19, 2025
@DaniGP17
Copy link
Contributor

DaniGP17 commented Feb 19, 2025

I hope this can help, function that crash: 48 8B C4 55 53 57 48 8D A8 ? ? ? ? 48 81 EC ? ? ? ? 0F 28 11.
First crash: It looks like is related to collision stuff, and the first param of the function is a nulltpr.
Second crash: Is in the same function but crash because the second param of the function is a nullptr.

@FingerlessGlov3s
Copy link
Author

One thing I have just realised it moved the game build from b3095 to b3258, I thought sv_enforceGameBuild was in use, but sadly not. Wish I knew this at the time now.

So both crashes are collision related, is what you think it maybe pointing the problem too?

@DaniGP17
Copy link
Contributor

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.
I think it would be useful to get a full dump so we can see the entire call stack.

@FingerlessGlov3s
Copy link
Author

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. I think it would be useful to get a full dump so we can see the entire call stack.

How do I go about getting a full dumb? Do I need to do something with WinDbg?

@Gogsi
Copy link

Gogsi commented Feb 19, 2025

You can configure FiveM to do full dumps - https://forum.cfx.re/t/enabling-and-uploading-full-client-dumps/1138940
Keep in mind they will be many GBs in size, but they compress really well in a zip, down to 1-2 GB. You'll have to then upload the zip to some cloud storage.

@FingerlessGlov3s
Copy link
Author

FingerlessGlov3s commented Feb 20, 2025

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

GTA5_b3095.exe!sub_1414B37A4

That was caused by someone being malicious and looked to be caused by prop prop_fragtest_cnst_04. Not sure if you need to spawn it in and then drive into it.

Unless someone else beats me to it, I'll see if I can make my client crash after work, to hopefully confirm the issue.

@DaniGP17
Copy link
Contributor

GTA5_b3095.exe!sub_1414B37A4

Can you share crash dump of that crash?

That was caused by someone being malicious and looked to be caused by prop prop_fragtest_cnst_04. Not sure if you need to spawn it in and then drive into it.

Unless someone else beats me to it, I'll see if I can make my client crash after work, to hopefully confirm the issue.

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.

@FingerlessGlov3s
Copy link
Author

Can you share crash dump of that crash?
Sadly I wasn't there to get one, but shall try get one after work.

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 🤔

YimMenu/YimMenu#2842 (comment)

@DaniGP17 DaniGP17 linked a pull request Feb 21, 2025 that will close this issue
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug crash triage Needs a preliminary assessment to determine the urgency and required action
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants