Bug #20

Critical Memory Leak Leading to Game Crashes After 60 Minutes

Status:	Open
Priority:	Critical
Added by:	lulu_26168 on February 21, '26
Assigned to:	Unassigned
Due date:
Reported for:	Update 4 Auto

Steps to Reproduce

1. Launch the game and host or join a session
2. Play normally or stay idle in the lobby/match
3. Monitor system memory; it will steadily increase without garbage collection
4. At approximately 60 minutes, the Host will drop all players, and both Host and Clients will experience a hard crash to the desktop
5. If the player attempts to relaunch the game immediately after the crash before Windows flushes the leaked memory, the game will crash instantly within 60 seconds with a 0x0 null pointer error

Explanation

Hello Development Team,

There is a critical memory leak issue in the current build of Neighbors Suburban Warfare. Regardless of whether I am playing as the Host or a Client, and regardless of in-game actions (even just idling in the lobby), the game consistently crashes right around the 60-minute mark (approx. 3600 - 3800 seconds).

According to the generated CrashContext.runtime-xml, both the physical memory and the virtual memory (page file) are completely exhausted at the time of the crash:

<MemoryStats.AvailablePhysical>0</MemoryStats.AvailablePhysical>

<MemoryStats.AvailableVirtual>0</MemoryStats.AvailableVirtual>

This memory exhaustion leads to the engine failing to allocate rendering resources, resulting in:
Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000010 (or 0x0).

Watchers

Watch