What causes an FMOD one-shot event leaking because it never stops?

You create an event instance for a one-shot but never call release, so even after the sound finishes the instance stays alive and the instance count climbs until you hit the limit.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix an FMOD One-Shot Event Leaking Because It Never Stops

Quick answer: For fire-and-forget one-shots, call start then release immediately so FMOD auto-frees the instance when playback ends; only retain a handle for events you must control later.

A one-shot should clean itself up. Releasing right after start tells FMOD to destroy the instance once it stops, preventing the slow leak that eventually exhausts the instance pool.

How to fix it

1. Start then release one-shots

For fire-and-forget sounds, call instance->start() then instance->release() immediately. FMOD frees the instance automatically when the event finishes.

2. Keep handles only for controllable events

Retain the EventInstance pointer only for looping or parameter-driven events you need to stop or modify; release everything else right away.

3. Watch the instance count

Use the FMOD profiler to confirm one-shot instance counts return to baseline after playback; a steadily rising count means a missing release somewhere.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

Reproduce it once with full context and the fix writes itself. The hunt is the expensive part.