Fix: Unity Job System Write Conflict Warning

Your Burst job system schedules two jobs to process the same NativeArray. Unity throws: “Job… has not completed yet. It writes the same array as Job…”. The warning is correct — you’d have a data race — but isn’t obvious how to fix.

Why the Safety System Blocks This

Unity’s job system tracks read/write access to each NativeContainer. Two parallel jobs with write access to the same container would race. The safety system refuses to schedule the second job until the first completes, and prints a warning to make this visible.

Fix 1: Chain via Dependencies

var handle1 = job1.Schedule(positions.Length, 64);
var handle2 = job2.Schedule(positions.Length, 64, handle1);
handle2.Complete();

Passing handle1 as the second argument tells the scheduler “don’t start job2 until job1 finishes”. Writes are serialized. Performance: job1 and job2 run sequentially, but main thread continues during both.

Fix 2: ReadOnly Where Possible

[BurstCompile]
public struct AnalyzeJob : IJobParallelFor
{
    [ReadOnly] public NativeArray<float3> positions;
    public NativeArray<float> distances;

    public void Execute(int index)
    {
        distances[index] = math.length(positions[index]);
    }
}

The [ReadOnly] attribute on positions tells the safety system: this job only reads. Another job can read positions in parallel without conflict.

Fix 3: NativeDisableParallelForRestriction

[BurstCompile]
public struct ScatterJob : IJobParallelFor
{
    [ReadOnly] public NativeArray<int> targetIndices;
    [NativeDisableParallelForRestriction] public NativeArray<float> results;

    public void Execute(int index)
    {
        int target = targetIndices[index];
        results[target] = math.sqrt(index);   // random index write
    }
}

This attribute disables the safety check for that container. Use only when you can guarantee that no two parallel iterations write to the same index — otherwise undefined behavior.

Fix 4: NativeQueue / NativeStream for Producers

For genuinely parallel writes to a shared destination, use a parallel-safe container:

[BurstCompile]
public struct ProduceJob : IJobParallelFor
{
    [WriteOnly] public NativeQueue<Event>.ParallelWriter queue;

    public void Execute(int index) {
        queue.Enqueue(new Event(index));
    }
}

NativeQueue’s ParallelWriter is designed for concurrent writes. Order isn’t guaranteed (queue ends up unordered) but the operations are race-free.

Diagnosing Excessive Completes

If your fix is “call CompleteAll”, the perf gain from Jobs evaporates because the main thread blocks. Look for opportunities to chain via JobHandle dependencies and to defer Complete to end-of-frame.

Verifying

Run with the Jobs Debugger open. The schedule should show no conflicts. Profiling should reveal parallel execution where independent, sequential where dependencies exist. No warnings in Player.log.

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

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

Verifying this fix in isolation is straightforward: reproduce the bug, apply the change, confirm the bug no longer reproduces. The harder verification is regression - did this fix introduce a new bug elsewhere? Run your standard regression suite, plus any tests that exercise the same code path with different inputs.

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

If this issue manifests under high load (many actors, many particles, many network connections), profile the post-fix code path with realistic counts. The original cost was a bug; the new cost is real work, and real work has a budget.

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

Modern engine versions ship better tooling for this kind of issue than older versions. If you're on an older release, the diagnostic step may take significantly longer because the tools you'd want don't exist yet. Sometimes the right answer is upgrading rather than fighting through limited tooling.

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

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.

“The Jobs safety system is your friend. Don’t suppress; fix the access pattern.”

Add [ReadOnly] reflexively to any NativeArray you only read — eliminates entire classes of warnings.