What is a pool size error in FiveM?
A pool size error is a FiveM client crash that happens when one of the GTA V engine's fixed-size object pools runs out of free slots. The engine reserves a set number of slots at startup for each kind of object it tracks, such as vehicles, peds, props or loaded texture dictionaries, and it cannot grow a pool while the game is running. When a server's scripts and custom content need one slot more than a pool holds, the game stops with an error that names the pool, in the form "<PoolName> Pool Full, Size == <number>".
What a pool is
A pool is a pre-allocated array with room for a fixed number of objects of one type. Creating an object takes a free slot, deleting it gives the slot back. Pools are fast and predictable, which is why game engines use them, but their size is decided when the game starts. Rockstar sized each one for the single-player game with a margin, in a file called gameconfig.xml.
There are a large number of pools. Some hold things players can see, such as vehicles, peds and objects. Others hold internal records: loaded texture dictionaries, drawables, fragments, animation data, script handles and so on. The error message tells you which pool overflowed, and that name is the most important clue to the cause. In FiveM the error reads <PoolName> Pool Full, Size == <number>.
Seeing this in your console? Paste the log into the Error Analyzer for the likely cause. Open the Error Analyzer
Why FiveM servers hit the limits
- Asset store pools fill when a server streams a very large number of custom assets. Every texture dictionary, drawable and fragment a server adds needs a slot in the matching store, so thousands of clothing items, props and vehicles add up.
- Entity pools for vehicles, peds and objects fill when scripts create entities and never delete them, or when a large number of players and spawned objects gather in one place.
- Map-related pools fill when many custom maps and interiors are loaded at once.
- Leaks make any of the above appear after hours of uptime instead of immediately. A crash that only happens late in a long session points to something being created repeatedly and not cleaned up.
How to fix it
- Read the pool name in the error and decide which of the groups above it belongs to.
- For asset pools, reduce the count. Remove unused resources, merge duplicates, and delete assets nobody uses. Files count, not megabytes: here a thousand small files are worse than ten large ones.
- For entity pools, find the script. Stop recently added resources one at a time and watch whether the crash returns. Garages, props, and ambient spawners that forget to delete what they create are the usual sources.
- Raise the pool if it is supported. Recent FiveM server versions provide an
increase_pool_sizecommand for server.cfg that adds slots to specific pools. It only takes effect at server start, and players' games restart once to apply it. Only some pools can be raised; vehicle and ped pools are not among them.
# One line per pool. TxdStore is on the allowed list; the amount is an example.
increase_pool_size "TxdStore" 6000Only pools on Cfx.re's approved list can be raised, and each has a cap. A single-player gameconfig.xml with enlarged pools does not apply to FiveM, so advice written for single-player mods will not carry over.
Raising a pool is not always the answer
A bigger pool postpones a leak; it does not stop it. If a script creates entities without deleting them, any pool size will be reached eventually. Bigger pools also use more memory on every client from the moment the game starts.
A pool error is also different from running out of streaming memory. Pools count objects; the streaming budget measures bytes. A server can crash on a full pool with small, well-optimized assets, and can lose textures with pools nowhere near full. See texture loss and the texture budget for the second case.
If you are unsure which problem you have, paste the full error into the Error Analyzer. The resource limits guide explains how far a server can be pushed before these limits appear.
Frequently asked questions
What causes a pool full error in FiveM?
The game needed one more object of a certain type than its fixed-size pool has slots for. Typical causes are a very large number of streamed custom assets, scripts that spawn entities without deleting them, or many custom maps loaded together.
Can I use a gameconfig.xml to fix pool errors on FiveM?
No. Custom gameconfig.xml files are a single-player solution. On FiveM, pools can only be raised with the increase_pool_size server command, and only for the pools Cfx.re allows.
Does optimizing textures fix pool size errors?
Usually not. Pool limits count objects rather than memory, so making files smaller does not help. Reducing the number of assets or fixing the script that leaks entities does.
Tools for this
Related guides
Related terms
Still need the car as a FiveM resource?
Paste a gta5-mods.com vehicle link and get a FiveM-ready resource with the manifest and metas in place. 3 free conversions, no signup.
- 3 conversions free, no account needed
- 2 more free if you leave an email
- After that: $15 once for unlimited conversions and the Pro tools. No subscription, 14-day refund policy