Players Crashes After Certain Hours

[i6aLeY]

What happened?

We have a FiveM server with 1000+ concurrent players, everything was working fine and we used to keep the server without restart for 20+ hours with no issues.

Around 20 days ago, after 8 or 10 hours any player joins the server and random online players crashes, and keep on crashing until we restart the server. The players drop from 1000+ to 800 or 600 any no one can rejoins the server.

We tried everything and revoked the latest changes, but the issue is still the same.

Everything working perfectly until a certain amount of hours pass and the restart solve the issue.

I attached the crashdump for some of the players.

Expected result

No random crashed for players

Reproduction steps

1. Keep the server online for +8 hours
2. Players start to crash for no reason
3. Players trying to rejoin crashes again

Importancy

Crash

Area(s)

FiveM

Specific version(s)

FiveM

Additional information

51f7mA5.zip CfxCrashDump_2025_05_19_20_28_12.zip CfxCrashDump_2025_05_19_20_39_45.zip CfxCrashDump_2025_05_19_20_43_40.zip CfxCrashDump_2025_05_19_20_45_31.zip cokbykv.zip

[ayazwai]

I think the problem may be due to the number of streams (add-ons) on your server. Although there is no definitive solution, maybe something may be exceeding the limit because the number of streams (add-ons) on the server increases according to player usage.

Try clearing unused stream content tools or props on the server every 10 or 30 minutes.

[CsyonDerEchte]

Same issue on my server. I just checked your crash and its exactly the same. It started after FiveM added this commit: https://github.com/citizenfx/fivem/commit/dfd119ff03798fbdbe09ba3a3a742b7b8eeee53b (The crashes started on May 18th, 2025) I haven't changed anything on my server in weeks, and it just started happening out of nowhere.

Players are crashing in waves, many of them experience the same crash at the same time and in the same location. Here's a screenshot someone sent me after reviewing the full client dump. According to him, there's an invalid chunk in the memory chunk list that's causing the crash:

[Gogsi]

Here's a screenshot someone sent me after reviewing the full client dump. According to him, there's an invalid chunk in the memory chunk list that's causing the crash:

Just putting a bit more info about this. This is technically a separate crash from the ones provided in this issue, but it could very well be related. The analysis in the screenshot is about the crash uranus-hamper-football at GTA5_b3258.exe!sub_141315788 (0x101). This is the generic allocate function that's hooked here. It crashes because it thinks it's found a chunk of memory that can be used to allocate but the pointer to that chunk is 0xFFFFFFFFFFFFFFFF. I'm really not sure how that could happen, seems like some massive corruption going on. It could be related to https://github.com/citizenfx/fivem/commit/dfd119ff03798fbdbe09ba3a3a742b7b8eeee53b as @CsyonDerEchte reports the crashes starting on the same day, but honestly I have no idea how.

As for the originally reported crash (violet-foxtrot-twenty at GTA5_b3258.exe!sub_141686780 (0x2d)), it seems to be happening in the fwExtensionList::Add method (hooked here), coming from various fragment related code (every crash seems different). Haven't taken a deep look into it but it's very likely related to https://github.com/citizenfx/fivem/commit/dfd119ff03798fbdbe09ba3a3a742b7b8eeee53b as the timing matches and the log files contain errors about corrected octants.

[i6aLeY]

Here's a screenshot someone sent me after reviewing the full client dump. According to him, there's an invalid chunk in the memory chunk list that's causing the crash:

Just putting a bit more info about this. This is technically a separate crash from the ones provided in this issue, but it could very well be related. The analysis in the screenshot is about the crash uranus-hamper-football at GTA5_b3258.exe!sub_141315788 (0x101). This is the generic allocate function that's hooked here. It crashes because it thinks it's found a chunk of memory that can be used to allocate but the pointer to that chunk is 0xFFFFFFFFFFFFFFFF. I'm really not sure how that could happen, seems like some massive corruption going on. It could be related to dfd119f as @CsyonDerEchte reports the crashes starting on the same day, but honestly I have no idea how.

As for the originally reported crash (violet-foxtrot-twenty at GTA5_b3258.exe!sub_141686780 (0x2d)), it seems to be happening in the fwExtensionList::Add method (hooked here), coming from various fragment related code (every crash seems different). Haven't taken a deep look into it but it's very likely related to dfd119f as the timing matches and the log files contain errors about corrected octants.

We tried removing the latest maps, and still faced the same issue.

Updated around 50% of the cars that show the Octant error in F8, but nothing changed.

Everything works fine and perfectly at the first 3-6 hours, then everything start to collapse.

[radium-cfx]

90% of all crashes with this signature come from one server, so this likely related to some "bad" assets.

Haven't taken a deep look into it but it's very likely related to https://github.com/citizenfx/fivem/commit/dfd119ff03798fbdbe09ba3a3a742b7b8eeee53b as the timing matches and the log files contain errors about corrected octants.

The crash was already happening before this was merged, so unlikely that this is related.

[CsyonDerEchte]

90% of all crashes with this signature come from one server, so this likely related to some "bad" assets.

Haven't taken a deep look into it but it's very likely related to dfd119f as the timing matches and the log files contain errors about corrected octants.

The crash was already happening before this was merged, so unlikely that this is related.

Hey, thx we finally tracked down the issue. It was caused by a tuning kit model from this mod: https://gta5-mods.com/vehicles/weevil-lb So yeah, it was due to "bad" assets, but it was a real pain to figure out the exact cause.