BlackWolf01

Title: Game crash (AccessViolationException) during Officer Involved Shooting callout — evidence cleanup on "Military technology crate" Summary: Game crashed to desktop with no LSPDFR crash report during the "Officer Involved Shooting" callout (City variant), while collecting/interacting with evidence. Log shows a native AccessViolationException thrown twice from OfficerInvolvedShootingCallout.CheckEvidence → ChillEntityCleanup.SafeDeleteNativeHandle, on an evidence prop labeled "Military technology crate". The first exception was caught and logged, the second one killed the process outright with no further log output and no LSPDFR crash report generated. Timeline: Callout OfficerInvolvedShootingCallout triggered and accepted, City variant, spawn pos ≈ -335.00, -1335.00, 31.00. Scene spawned successfully (captain, officer, victim all valid). During evidence collection, first AccessViolationException thrown: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. at Rage.Native.NativeFunction.CallByAddress(IntPtr address, Type returnType, NativeArgument[] arguments) at Rage.Native.NativeFunction.CallByName(String nativeName, Type returnType, NativeArgument[] arguments) at Rage.Native.NativeFunction.CallByName[ReturnType](String nativeName, NativeArgument[] arguments) at chillLScallouts.ChillEntityCleanup.SafeDeleteNativeHandle(Int32 handle, String owner, String label) at chillLScallouts.OfficerInvolvedShootingCallout.<CheckEvidence>g__TryCollect|142_0(Boolean& found, Int32& handle, Vector3 pos, String label, String msg, <>c__DisplayClass142_0& ) at chillLScallouts.OfficerInvolvedShootingCallout.CheckEvidence(Ped player, Boolean yPress) at chillLScallouts.OfficerInvolvedShootingCallout.Process() Immediately followed by: [OIS] SafeDeleteNativeHandle still exists: Military technology crate Game survived this occurrence and continued running normally for ~56 more seconds. Same exact exception (same stack trace, same code path) thrown again ~56 seconds later. This time no follow-up log line was written at all — the log file ends abruptly right after this second exception. No clean shutdown, no LSPDFR crash report was generated.