[Bug] Pool 0x5411E15C (60000 x 208 B) overflows in Paleto Forest on the stock world, crashes with "Pool Full, Size == 60000", pool cannot be raised

[phiomet]

Summary

The client crashes with "Assertion failed | 0x5411E15C Pool Full, Size == 60000" when spawning at (-671.3, 4879.8, 203.2), a hillside in Paleto Forest about 200 m above ground. The pool has 208-byte items and 60000 slots. In the Pool Tool it climbs while the character falls and terrain streams in (59072 -> 59512 of 60000), then the client crashes. The pool is unnamed in the pool list and increase_pool_size has no effect on it. Reproduced without any custom maps, MLOs, ymaps or IPLs. The Pool Tool shows 50823 / 60000 on Legion Square for comparison.

Issue type

Client

Repro rate

Always

Server build version

b170

OS

Windows 11 24H2

CPU

AMD Ryzen 7900X3D

GPU

Radeon 7900XT

RAM

64 GB DDR5-6000

Storage type

SSD NVMe

Connection type

Ethernet

ISP and bandwidth

Magenta 600/60

DxDiag

No response

Network graph

No response

Platform

Windows

OS version / distribution

Windows 11 24H2

CPU

AMD Ryzen 7900X3D

RAM

64 GB DDR5-6000

Using txAdmin?

Yes

Hosting provider

Self-hosted

Machine type

Dedicated

/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

1. Start a local FXServer (b170) with only the stock resources and a small character-selection script. No custom maps/MLOs/IPLs.
2. Open the Pool Tool in the client (F8: con_poolInspector true).
3. Spawn the player at (-671.3, 4879.8, 203.2) with SetEntityCoordsNoOffset.
4. Watch pool 0x5411E15C (208 B, 60000 items): it rises from ~59000 to ~59500 while terrain streams in.
5. The client crashes with Pool Full, Size == 60000.

Expected Behavior

The stock world should be loadable at any spot without hitting a fixed limit, or the pool should be raisable via increase_pool_size like PortalInst after #455.

Actual Behavior

The client crashes with "Assertion failed | 0x5411E15C Pool Full, Size == 60000". The pool 0x5411E15C is already at 99-100 % at this spot on the stock world and cannot be raised with increase_pool_size. On Legion Square the same pool is at 50823 / 60000 (84.7 %).

Evidence

Pool Tool recordings:

• 2026-10-27_09-48-27.mp4: Paleto hillside, a few custom maps, pool at 59810 -> 59968
• 2026-10-27_09-54-08.mp4: Legion Square, pool at 50823 (84.7 %)
• 2026-10-27_10-03-30.mp4: Paleto hillside, no custom maps, pool 59072 -> 59512, then crash

2026-10-27_09-54-08.mp4

2026-10-27_10-03-30.mp4

2026-10-27_09-59-27.mp4

Additional Context

de37aa78-40dd-40e7-bfb4-f92bbc92b548, cd980b51-87b2-47b1-a59e-c9ec90f71faa, d8b421cc-dbcf-4b00-80c4-870372a0dee7

Client build early-access/b167 (from the in-game overlay), server b170.
I set increase_pool_size to the maximum for every pool on the limits list (DwdStore, DrawableStore, TxdStore, AnimStore, fwDynamicArchetypeComponent, FragmentStore, MapDataStore, MapTypesStore, StaticBounds, InteriorProxy, InteriorInst, MetaDataStore, NavMeshes). The crash still reports Size == 60000, so none of them is the affected pool. The client log shows "Didn't add pool to the list due to currentPoolNameHash being equal to 0." (same as #524).
Related: #316, #455, #524.

[wolfram-cfx]

Thanks, we will increase this pool to match the FiveM Legacy size of this in the next patch.

[Gogsi]

Hello,
A fix for this issue has been implemented in November 11 patch for FiveM for GTAV Enhanced. Please try again and let us know if the issue persists. Thanks for your help!