Fix: Unity NativeArray Disposed While Job Still Running

Here is how to fix Unity throwing InvalidOperationException: The Unity.Collections.NativeArray has been deallocated when your job tries to write to it. You scheduled a job, kept a reference to the input array, and disposed it before the job finished. Or you forgot to dispose at all and the leak detector trips on shutdown. Both share the same fix: explicit lifecycle for native containers.

The Symptom

Console error: InvalidOperationException: The Unity.Collections.NativeArray has been deallocated, it is not allowed to access it. Or in Editor.log on quit: A Native Collection has not been disposed, resulting in a memory leak. The job runs once or twice fine then errors on a subsequent frame.

What Causes This

Dispose before Complete. Calling Dispose on a NativeArray that is still in flight inside a job triggers the safety system error.

Forgetting to Complete. A job scheduled and forgotten lingers; if the array goes out of scope without dispose, the leak detector flags it.

Wrong allocator for DeallocateOnJobCompletion. The attribute only works with TempJob allocator. With Persistent, the auto-dispose does not trigger.

Job depending on already-disposed handle. Chaining a new job onto a JobHandle that completed and disposed its dependencies leaves the new job dependent on freed memory.

The Fix

Step 1: Always Complete before Dispose.

using Unity.Collections;
using Unity.Jobs;

public class RunJob : MonoBehaviour
{
    private NativeArray<float> data;
    private JobHandle handle;

    void Update()
    {
        data = new NativeArray<float>(1024, Allocator.TempJob);

        var job = new WriteJob { output = data };
        handle = job.Schedule(data.Length, 64);

        handle.Complete();   // MUST happen before dispose

        Debug.Log(data[0]);
        data.Dispose();
    }
}

Step 2: Use DeallocateOnJobCompletion for one-shot temps.

[BurstCompile]
public struct WriteJob : IJobParallelFor
{
    [DeallocateOnJobCompletion]
    public NativeArray<float> output;

    public void Execute(int i)
    {
        output[i] = i * 0.5f;
    }
}

The job system disposes output automatically after the job completes. No manual Dispose needed.

Step 3: For persistent allocations, dispose in OnDestroy.

public class PersistentNativeOwner : MonoBehaviour
{
    private NativeArray<int> persistent;

    void Awake()
    {
        persistent = new NativeArray<int>(1024, Allocator.Persistent);
    }

    void OnDestroy()
    {
        if (persistent.IsCreated)
        {
            persistent.Dispose();
        }
    }
}

Always check IsCreated before dispose to handle the case where Awake never ran (component disabled).

Step 4: Chain dependencies safely.

JobHandle h1 = job1.Schedule(arr.Length, 64);
JobHandle h2 = job2.Schedule(arr.Length, 64, h1);   // h2 depends on h1
h2.Complete();   // completes both
arr.Dispose();

Step 5: Enable Jobs Debugger to catch issues early. Open Jobs → JobsDebugger and enable. The safety system catches misuse and reports source locations. Disable for shipping builds (it is editor-only by default).

Avoiding Leaks On Application Quit

For singletons holding native arrays, hook Application.quitting:

void Awake()
{
    Application.quitting += () => {
        if (data.IsCreated) data.Dispose();
    };
}

Understanding the issue

This bug class falls into a pattern that's worth understanding beyond the specific case. In Unity Engine, the underlying behavior is shaped by how the engine layers its abstractions - the public API you call, the runtime systems that respond, and the platform-specific implementations underneath. A bug at any layer can produce symptoms that look like they originate at a different layer. Triaging effectively means recognizing which layer the symptom belongs to, even when the gameplay code is what's visible.

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

The triage path for this kind of bug is long. The symptom appears in gameplay, but the cause is in a different system. The reporter describes the gameplay effect; the engineer has to translate that into a hypothesis about the underlying cause. Misdirection is common.

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

There's almost always a less obvious case where the same problem applies. The reported case is the one a player hit; the related cases hide because they're rarer or affect fewer players. After fixing the reported case, search the codebase for the pattern - one fix often unlocks several.

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

For shipping titles with a long support window, watch for this issue resurfacing after dependency updates. Engine upgrades, driver updates, OS releases - each one can resurface a bug class you thought you'd fixed because the underlying behavior changed slightly. Regression tests catch the obvious ones; player reports catch the rest.

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

The diagnostic tools available depend on your engine and platform. Use the engine's native profilers and debug overlays before reaching for external tools. The native tools have context that external tools lack - they know which subsystem owns the code, which assets are loaded, and what state the engine is in.

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

The tooling around this bug class matters as much as the fix itself. Good logging, accessible profilers, and clear error messages turn 30-minute investigations into 5-minute ones. If your project doesn't have visibility into this code path, the first fix should add the visibility - the second fix uses it.

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

Platform-specific edge cases are worth enumerating explicitly. iOS handles backgrounding differently than Android; Windows handles focus changes differently than macOS. A fix that works on the development platform may not work on every target. Test on each shipping platform deliberately.

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

Document the fix and its rationale in the commit message or attached engineering doc. Future engineers will encounter related issues; the rationale tells them whether your fix is reusable or specific to the case at hand. Without rationale, the fix gets reverted or copied incorrectly.

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.

“Jobs run async. Native containers are sync. Bridge them with Complete or DeallocateOnJobCompletion.”

Related Issues

For Burst compile errors, see IJobParallelFor Burst Error. For ECS aspects, see ECS Aspects Not Registering.

Complete before Dispose. DeallocateOnJobCompletion for temps. OnDestroy for persistent. No leaks.