[Bug] AddDoorToSystem sometimes breaks client-side object, ped & vehicle creation

[1A3Dev]

Summary

AddDoorToSystem sometimes causes an exception which can break other client-side natives from working correctly

Issue type

Client

Repro rate

Always

Server build version

FXServer-early-access b94 win32

OS

Windows 11 25H2

CPU

AMD Ryzen 5 5600X

GPU

NVIDIA RTX 3070 Ti

RAM

32 GB DDR4

Storage type

SSD NVMe

Connection type

None

ISP and bandwidth

No response

DxDiag

No response

Network graph

No response

Platform

None

OS version / distribution

No response

CPU

No response

RAM

No response

Using txAdmin?

None

Hosting provider

None

Machine type

None

/perf endpoint output

No response

DDoS protection

No response

ulimit -n value (Linux only)

No response

Docker Compose file (Docker only)

No response

Steps to Reproduce

I don't have super solid reproduction steps and it doesn't seem to happen at a specific amount of doors and also doesn't occur every time the resource is restarted.

1. Use ox_doorlock and add a lot of doors (seems to usually occur around 600+ doors)
2. Restart the resource a few times

Expected Behavior

It should add the door correctly without any exception and shouldn't break other natives

Actual Behavior

It doesn't add the door and causes triggers of some other natives such as CreatePed & CreateObject that are ran afterwards (even in other scripts) to fail with the same exception (exception at game RVA 0x149A81)

Evidence

Additional Context

I've not had this issue at all on legacy however for enhanced it seems to happen every time I join after the server is started

[Gogsi]

A fix for this bug has been implemented and is available in August 11 Patch. Please try again and let us know if the issue persists. Thanks for your help!