Fix: Unity Addressables Async Handle Leak

Game runs fine for ten minutes. Then memory creeps. Then a Bundle Failed To Mount crash on Android. Addressables holds refcounts behind handles, and forgotten handles never decrement.

The Symptom

Memory grows over time even though gameplay should free assets. Editor Addressables window shows hundreds of loaded assets that should be gone. Console may print “Cannot release a null Asset Bundle” warnings.

The Fix Pattern

using UnityEngine;
using UnityEngine.AddressableAssets;
using UnityEngine.ResourceManagement.AsyncOperations;

public class EnemyLoader : MonoBehaviour
{
    public AssetReferenceGameObject enemyRef;
    private AsyncOperationHandle<GameObject> _handle;
    private GameObject _instance;

    async void Start()
    {
        _handle = enemyRef.InstantiateAsync(transform);
        _instance = await _handle.Task;
    }

    void OnDestroy()
    {
        if (_instance != null)
            Addressables.ReleaseInstance(_instance);
    }
}

One handle stored, one release in OnDestroy.

For Plain Asset Loads

private AsyncOperationHandle<Texture2D> _texHandle;

async Task LoadIcon()
{
    _texHandle = Addressables.LoadAssetAsync<Texture2D>("icons/sword");
    var tex = await _texHandle.Task;
    iconImage.texture = tex;
}

void OnDestroy()
{
    Addressables.Release(_texHandle);
}

Detecting Leaks

Addressables → Profiler → Asset Manager. Hierarchical view of every loaded asset and its refcount. Numbers that grow without an obvious owner are leaks.

Project Settings → Addressables → tick “Log Runtime Exceptions” and “Send Profiler Events.” Now leaked handles produce console warnings on application quit, which catches them in development builds.

Pool Pattern for Frequent Loads

For projectiles or enemies you load thousands of times, use addressables once to load the prefab handle, then pool the instances yourself with Object.Instantiate. Release the prefab handle on level unload.

Verifying

Load a scene that uses Addressables, unload it, GC, check Profiler → Memory. Resources should drop. Repeat 10x; memory should stabilize. If it grows linearly, something isn’t releasing.

Understanding the issue

Addressables decouple asset references from filesystem paths. The flexibility comes with configuration cost; bugs in the configuration manifest as 'this thing should load but doesn't'.

The specific bug described above is the kind that surfaces during integration rather than unit testing. It depends on a combination of factors: the asset configuration, the runtime state, the platform's specific behavior. In isolation, each piece looks correct; in combination, the bug emerges. This is why thorough integration testing - playing the actual game in realistic conditions - catches things that automated tests miss.

Why this happens

This bug class disproportionately affects late-stage development. The work to surface it is interactive testing in realistic conditions, which only really happens after the gameplay is in place and assets are populated. Catching it early requires deliberate testing of conditions that look unimportant.

At the engine level, the behavior comes from a deliberate design decision in Unity. The engine team chose a particular trade-off - usually performance versus convenience, or generality versus specificity - and that trade-off has consequences when you push against it. Understanding the trade-off is what turns 'this bug is mysterious' into 'this bug is the expected consequence of this design'.

Verifying the fix

After applying the fix, the verification step has three parts: confirm the original repro is resolved, confirm no obvious regressions in adjacent functionality, and (for shipping titles) deploy to a small player cohort first and watch the crash and report rates. Each step catches something the others miss.

Reproducibility is the prerequisite for verification. If you can't reliably reproduce the bug pre-fix, you can't reliably verify it post-fix. Spend time getting a clean reproduction before you write any fix code. The fix is fast once you understand the reproduction; the reproduction is the slow part.

Variations to watch for

Related bug classes often share the same root cause. If you find yourself fixing this issue, look for cousins: similar symptoms in adjacent systems, the same data flow but a different value, or the same fix pattern in another module. The catalog of 'we've seen this before' becomes valuable institutional knowledge.

Adjacent bugs often share a root cause. After fixing the case you've found, spend an hour searching the codebase for similar patterns. What's the same call with different arguments? The same data flow with a different entity type? The same lifecycle issue in a sibling system? Each match is a candidate for the same fix, or a related fix that prevents future bugs of the same class.

In production

In shipping builds, this issue may interact with other production-only behavior. Stripping, encryption, asset bundling, and platform-specific code paths can each modify the symptoms. When players report a related issue, capture build SHA, platform, and any feature flags - those three fields cover most of the production-only variations.

When triaging a similar issue in production, prioritize gathering data over hypothesizing causes. A player report describes a symptom; what you need is a build SHA, a session timestamp, and ideally a screen recording or session replay. With those, the bug becomes tractable. Without them, you're guessing at hypothetical reproductions that may not match what the player actually hit.

Performance considerations

Performance implications matter when this bug class scales with player count or asset count. A bug that fires once per session is annoying; a bug that fires once per frame compounds. After fixing, profile the affected code path under realistic load. The fix that's correct for one entity may be too slow for ten thousand.

Diagnostic approach

Before applying any fix, gather enough context to be confident you're addressing the actual cause and not a similar-looking symptom. The cheapest diagnostic step is reproducing the bug deterministically - if you can't get the same failure twice in a row, your fix attempts will be hard to evaluate. Lock down the reproduction first.

For Unity-specific diagnostics, the editor's profiler is the canonical starting point. Capture a representative frame with the symptom present; compare against a frame without the symptom; the diff often points directly at the cause. If the symptom is non-deterministic, capture multiple frames and look for the pattern - the cause is usually a state transition or a specific input value rather than a continuous effect.

Tooling and ecosystem

Third-party plugins often provide better diagnostics for their own behavior than the engine does. If the affected code is in a plugin, check the plugin's documentation for debug modes, verbose logging, or inspector tools - these can save hours of investigation when they exist.

Within Unity, the relevant diagnostic surfaces include the standard frame debugger, memory profiler, and engine-specific debug overlays. Each one shows a different facet of what's happening. The frame debugger reveals draw call ordering and state transitions; the memory profiler shows allocation patterns; the debug overlay reveals per-system state. Bugs that resist one tool usually surrender to another - the trick is knowing which tool to reach for first.

Edge cases and pitfalls

Boundary conditions deserve specific testing attention. What happens when the input is zero, maximum, negative, or NaN? What happens at the start of a session vs hours in? What happens at the boundary between two systems handling the same data? These are where bugs hide and where regression tests are most valuable.

When writing a regression test for this fix, focus on the boundary conditions that surfaced the original bug. Tests that exercise the happy path catch obvious regressions; tests that exercise the boundary catch the subtler regressions that look like new bugs but are really the original returning. The latter are the tests that earn their keep over the long life of the project.

Team communication

When this bug class affects multiple teams (often the case for cross-system issues), early communication prevents duplicate work. The team that owns the symptom may not own the cause. A 15-minute conversation at the start of triage often saves hours of independent investigation.

If this fix touches a system several engineers work in, a short writeup in the team's engineering channel helps. Not a full design doc - a paragraph explaining what was wrong, what's fixed, and what to watch for. Future engineers encountering similar symptoms will search for the fix; making it findable is a small investment that pays back later.

“Hold the handle. Release in OnDestroy. ReleaseInstance for instantiated. Memory stays flat.”

Related Issues

For Addressables remote cache stale, see cache stale. For asmdef circular, see asmdef.

Hold. Release. Refcount returns to zero.