Since updating to 1.30.164289 our community dedicated server crashes several times a day with STATUS_HEAP_CORRUPTION (0xc0000374). We did not see this on 1.30.164200.

Every crashing session shows the same sequence in the RPT:

1. While the server is still starting, clients connect and leave again ("[Disconnect]: Client <id> early disconnect").

2. When "Player connect enabled" is reached, the server still adds these already-gone clients to the login queue.

3. In the same frame it removes them again ("Remove <id> from login queue", "Player destroy <id>"), followed by the error "NETWORK (E): server: Player dpid=<id> index not removed".

4. Later the server crashes with 0xc0000374 inside the heap allocator while replicating the world to a joining player (last RPT line: "Replicate game state '<player>'"). In two cases this was the very next player, about 2 seconds later; in others it was minutes to about an hour later.

From our logs: every crashing session contains these queue removals, and 20 of the 22 removed clients had an early disconnect before. None of our crash-free sessions has a single queue removal, although they also had early disconnects. All minidumps show the same engine code path (network replication -> RtlAllocateHeap / RtlFreeHeap) with no script on the stack. It looks like the entry of a client that left during startup is freed while it is still referenced (use-after-free).

Anonymised RPT excerpt from one crash (times relative to "Player connect enabled", client IDs replaced):

t-120.0s [Disconnect]: Client A early disconnect

t-15.4s [Disconnect]: Client B early disconnect

t+0.0s Player connect enabled

t+2.4s [Login]: Adding player A to login queue at position 10

t+2.4s [Login]: Adding player B to login queue at position 21

t+2.4s [Login]: Remove A from login queue (index 15)

t+2.4s [Disconnect]: Player destroy A

t+2.4s NETWORK (E): server: Player dpid=A index not removed

t+2.4s [Login]: Remove B from login queue (index 23)

t+2.4s [Disconnect]: Player destroy B

t+2.4s NETWORK (E): server: Player dpid=B index not removed

t+4.5s NETWORK: Replicate game state 'C'

t+4.5s ENGINE (F): Crashed

Crash log: Reason: SEH exception thrown. Exception code: 0xc0000374, stack RtlIsZeroMemory -> misaligned-access -> RtlFreeHeap (other crashes: RtlAllocateHeap) called from DayZServer_x64.exe +0x1f9833 / +0x1f97b4 / +0x5fa2f3. Minidumps and full logs can be shared privately with the team.

1. Run a busy dedicated server on 1.30.164289 and restart it, so that many players reconnect while it is still loading

2. Have one or more clients connect during startup (before "Player connect enabled") and disconnect again before startup finishes

3. When connections open, the server adds these clients to the login queue, removes them immediately and logs "index not removed"

4. The server crashes with 0xc0000374 shortly after, during "Replicate game state" for a joining player

Clients that disconnected during startup are not added to the login queue, or are removed cleanly without leaving a dangling player index. The server does not crash.