-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Process crash captured, GTA5_b3095.exe!sub_1043C60C0 (0x47) #2448
Comments
Thanks for the report. A very old crash fix needs updating for b3095 as the function underwent some changes (the call site also changed; making detecting this change even more difficult). |
Have been trying to investigate the root cause of this crash as the initial fix for this was committed well over six years ago (am hoping to improve this fix). Our crash statistics indicate that this seems more frequent on specific servers and given the location of the crash I would presume is (vehicle) asset related. Few questions:
|
Thanks for the reply. I've asked our vehicle devs and I await a reply about the This crash appears to happen for all users but happens more frequently for users with low-powered PCs |
@prikolium-cfx We've updated our server artifact build to 8102 and we're still getting our players crashing with the above. |
Changes are currently on canary/latest at the moment (unrelated to server artifact version). |
Ah I see, whats the usual timeline until it reaches Release / Stable version? Just wondering whether we get our players to switch to Canary or not |
At some point in the near future Release should receive more frequent updates, e.g., bimonthly/bi-the-one-that-means-every-two-weeks or something similar (for reference, we are approaching ~2 months since our last actual Release update). |
Hello, any update on that? Still happening for us :/ |
What happened?
We are having reports of players in our server randomly crashing with:
Seemingly random, players all doing different things in different locations when this crash occurs.
I did a minimum lookup using a player's crashlog and all it tells us is that we are referencing memory that does not exist.
We've tried everything to trace what this is.
Any ideas of what this is or how we can trace what it is?
Expected result
No crash
Reproduction steps
No idea at the moment, appears to happen randomly
Importancy
Crash
Area(s)
FiveM, FXServer, OneSync
Specific version(s)
ArtifactVersion 7595
Additional information
No response
The text was updated successfully, but these errors were encountered: