Quick Object Pool Pro

Two lines. No manager object, no packages, nothing to add to a scene.

var bullet = Pool.Spawn(bulletPrefab, muzzle.position, muzzle.rotation);

Pool.Despawn(bullet);

Twenty thousand spawn-and-despawn pairs allocate 0 bytes. The same loop with Instantiate and Destroy allocates about 47 bytes a pair and hands the bill to the garbage collector, which pays it in one visible hitch some frames later. That number is measured, not claimed, and the demo scene puts it on screen while you watch.

NOTHING ALLOCATED ON THE HOT PATH

• No LINQ, no closures, no boxing, and no GetComponent

• Every component a pooled object needs is looked up once, when the object is built, and kept with it

• Per-object bookkeeping is a struct, so tracking an object costs nothing either

A WINDOW THAT TELLS YOU THE NUMBER

• Live hit rate, peak in use, and objects built

• "23 spawns have had to build an object mid-game. Prewarming 31 would have covered every one of them." — with a button that writes it into the profile

• Guessing pool sizes is the part nobody enjoys. This measures it from what your game actually did.

LEAK DETECTION WITH CALL SITES

• Objects that went out and never came back, how long they have been gone, and the line of code that spawned them

• A pool cannot reuse what nobody returns, so a leak shows up as a pool that only ever grows — and the cause is invisible

• This names it instead. Select the object straight from the list.

PREWARMING THAT DOES NOT HITCH

• Building a thousand objects in one frame is the very freeze pooling exists to prevent

• Prewarm is spread over frames against a millisecond budget

• The pool measures what a creation actually costs on the machine it is running on, so the budget means the same thing on a laptop and on a console

THE REST

• THREE WAYS TO RUN DRY — grow, recycle the oldest, or refuse and let the caller decide. Each explained in the inspector, including the trap: grow plus a ceiling behaves like refuse once it hits the ceiling.

• AUTO-RETURN — after a timeout counted in game time, so pausing the game pauses it too; or when an effect has played and finished. An effect is a prefab made only of particle systems, audio, lights and scripts, so an enemy is never sent back because its spawn puff or its footstep sound ended.

• IPooled — OnSpawned and OnDespawned for resetting state. A pooled object is not a new object; its fields hold whatever the last user left behind, and that is the single most common way pooling introduces bugs.

• THE AWKWARD CASES ARE HANDLED — despawning twice, despawning something that never came from a pool, an instance somebody else destroyed, a scene unload (whatever was spawned in that scene goes back to the pool instead of carrying on in the next one). None of them corrupt the free list, and the ones that are your bug say so.

• A DEMO SCENE IN THE PACKAGE — two guns firing the same prefab at the same rate, one pooled and one not, with managed memory growth and worst frame time on screen.

• PURE-C# POLICY — how much to prewarm this frame, what size to suggest, what counts as a leak. No Unity in it, so the inspector's numbers and the running game's numbers cannot disagree.

NO DEPENDENCIES

Not "no third-party dependencies" — no Unity packages either. Nothing to install, no TextMeshPro, no uGUI. It imports into a bare Built-in project with zero console errors, and works the same in URP and HDRP.