fivem icon indicating copy to clipboard operation
fivem copied to clipboard

Process crash captured, GTA5_b3095.exe!sub_1043C60C0 (0x47)

Open Jamesking56 opened this issue 3 months ago • 3 comments

What happened?

We are having reports of players in our server randomly crashing with:

[    463438] [b3095_GTAProce]             MainThrd/ 
[    467735] [b3095_DumpServ]                15796/ Process crash captured. Crash dialog content:
[    467735] [b3095_DumpServ]                15796/ GTA5_b3095.exe!sub_1403C60C0 (0x47)
[    467735] [b3095_DumpServ]                15796/ An error at GTA5_b3095.exe!sub_1403C60C0 (0x47) caused FiveM to stop working. A crash report is being uploaded to the FiveM developers.
[    467735] [b3095_DumpServ]                15796/ 
[    467735] [b3095_DumpServ]                15796/ Legacy crash hash: venus-kentucky-sierra
[    467735] [b3095_DumpServ]                15796/ Stack trace:
[    467735] [b3095_DumpServ]                15796/   GTA5_b3095.exe!sub_1403C60C0 (0x47)
[    467735] [b3095_DumpServ]                15796/   GTA5_b3095.exe!sub_1403884D0 (0x14f)
[    467735] [b3095_DumpServ]                15796/   GTA5_b3095.exe!sub_1412D1894 (0x7c)
[    467735] [b3095_DumpServ]                15796/   GTA5_b3095.exe!sub_14035366C (0x38)
[    467735] [b3095_DumpServ]                15796/   GTA5_b3095.exe!sub_140021270 (0x5c)
[    467735] [b3095_DumpServ]                15796/   GTA5_b3095.exe!sub_14162EDDC (0xe3)
[    467735] [b3095_DumpServ]                15796/   GTA5_b3095.exe!sub_140001484 (0xf)
[    467735] [b3095_DumpServ]                15796/ 
[    469625] [b3095_DumpServ]                15796/ Crash report service returned si-7a93f8ba1f2a4a839ef1415d9fc14c79

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

Jamesking56 avatar Apr 06 '24 22:04 Jamesking56

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).

gottfriedleibniz avatar Apr 24 '24 00:04 gottfriedleibniz

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:

  1. Would you happen to stream any custom vehicle fragments without a chassis_dummy bone?
  2. Does this crash seem to occur for only a specific subset of users? If so, is there any way I could get a full dump out of this?

gottfriedleibniz avatar Apr 25 '24 16:04 gottfriedleibniz

Thanks for the reply. I've asked our vehicle devs and I await a reply about the chassis_dummy bone.

This crash appears to happen for all users but happens more frequently for users with low-powered PCs

Jamesking56 avatar Apr 26 '24 08:04 Jamesking56

@prikolium-cfx We've updated our server artifact build to 8102 and we're still getting our players crashing with the above.

Jamesking56 avatar May 07 '24 14:05 Jamesking56

Changes are currently on canary/latest at the moment (unrelated to server artifact version).

gottfriedleibniz avatar May 07 '24 14:05 gottfriedleibniz

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

Jamesking56 avatar May 07 '24 14:05 Jamesking56

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).

gottfriedleibniz avatar May 07 '24 14:05 gottfriedleibniz