Game version: 1.30.164078 (Windows Server 2022, x64)

Map: Nasdara (dayzOffline.nasdara)

Reproducibility: Rare / random (once in about 2,300 suicide emotes in our logs)

The dedicated server crashed with an unhandled access violation when a player finished the suicide emote (EmoteSuicide with a StoneKnife). The crash happens in the engine when SetHealth is called from EmoteManager.KillPlayer, at the moment the character dies.

Crash log excerpt:

Unhandled exception

Reason: Access violation. Illegal write by 0x7ff775b3ef07 at 0xffffffffffffffff

Class: 'SurvivorBase'

Function: 'SetHealth#92403'

Stack trace:

scripts/3_Game/entities/object.c:1079 Function SetHealth#92403

scripts/4_World/classes/emotemanager.c:797 Function KillPlayer

scripts/4_World/classes/emotemanager.c:36 Function OnAnimationEvent

Fault code bytes: F0 FF 00 48 89 45 50 4C 8D 7D 50 BF 02 00 00 00

RPT right before the crash:

13:47:24.78 CHAR_DEBUG - KILL

13:47:24.78 player <name> (dpnid = 488152717)

13:47:24.78 Identity: playerID = 414 , charID = 414

13:47:24.79 NETWORK : Simulate networked player entity SurvivorM_Taiki:49441

13:47:24.79 ENGINE (F): Crashed

1. The player was killed in PvP (13:46:38).

2. The player respawned as a fresh character (13:46:57).

3. About 18 seconds later the player started EmoteSuicide with a StoneKnife (13:47:15).

4. When the emote finished, the character died (13:47:24) and the server crashed in the same frame.

Expected result:

The player dies normally and the server keeps running.

Actual result:

The server crashes with an access violation (illegal write at 0xffffffffffffffff). This looks like an invalid or freed entity pointer inside SetHealth.