[Bug] [.NET10/C#] Collection was modified; enumeration operation may not execute.

[shloooo]

Summary

After few minutes on the server, my server crashs with the following error:

[23:48:53] [error] [citizen-scriptin] Unhandled exception while executing tick handler: System.InvalidOperationException: Collection was modified; enumeration operation may not execute.
   at CitizenFX.Base.NativeApi.ResetStrings()
   at CitizenFX.Base.BaseEntrypoint.BaseTick()
   at CitizenFX.Host.Host.TickScript(IntPtr scriptPtr)

As this is an bug in .Net10 Server Core, an reproduction resource shouldn't be needed at all. Tbh i dont even know how this happen
This error occurs since Hotfix #2 got released.

Issue type

Server

Repro rate

Always

Server build version

FXServer-early-access b94 win32

OS version / distribution

Windows 11 (26H2 / 26300.8772)

CPU

AMD Ryzen 5 5600

RAM

64 GB DDR4

Using txAdmin?

No

Hosting provider

Self-hosted

Machine type

Dedicated

Steps to Reproduce

As the error occurs random, there is no real step to reproduce this.

Expected Behavior

The server shouldn't crash

Actual Behavior

The server crashs

Evidence

[europium-cfx]

Hey! Thanks for the report.

We'll look into the issue stated in the error message, however that theoretically should not lead to a crash. Is this the last message in the logs before server process stops? Could you please check what was the exit code of the server process?

[shloooo]

Hey!

It's the last message that appears in the log, yes. There is no other error.

The exit code was -1073740940

[europium-cfx]

Yeah, then it makes sense (the exit code is heap corruption). Could you please tell me - do you use new CitizenFX.FiveM.Server NuGet, or do you run Legacy backwards compatibility mode?

This error seems to be caused by calling natives from a background thread. While this issue specifically should not happen (the fault in the C# native invocation logic), as far as I know none of the natives are considered thread-safe, and therefore they are not guaranteed to work properly when called from a non-main thread.

We will fix this specific issue and add ways to catch non-main thread native calls in one of the coming patches.

[shloooo]

yes, the new NuGet with v0.0.2-alpha

[Gogsi]

A fix for this bug has been implemented and is available in the latest patch b96/97. Please try again and let us know if the issue persists. Thanks for your help!

[shloooo]

Still happens with b96