Fix: Unity IJobParallelFor Burst Compile Error

Here is how to fix Unity IJobParallelFor structs that produce Burst compile errors. You define a job, schedule it, and the console fills with red: BC1042: The managed function pointer cannot be used in Burst or error MJ0006: Cannot access NativeArray in parallel for loop. The fix is almost always one of two things: managed type leakage, or missing ReadOnly/WriteOnly attributes.

The Symptom

Compile errors only when Burst is enabled. With Burst disabled, the job runs slowly but correctly. With Burst on, the console emits BC* (Burst Compile) errors mentioning function pointers, managed methods, or boxed values. Or you hit safety errors at scheduling time accusing the job of unsafe parallel access.

What Causes This

Managed types in the job struct. Burst compiles to native code. It cannot use the managed runtime: no string, no class instances, no delegates that capture managed state, no List<T> or Dictionary<K,V>.

Calls to UnityEngine APIs. Debug.Log, Mathf.Sin, Vector3.Distance, and most UnityEngine namespace functions are not Burst-compatible. Use Unity.Mathematics equivalents (math.sin, math.distance, float3).

Multiple writes to a parallel-for array. IJobParallelFor allows writes only to the index passed to Execute(int index). Writing to other indices is a data race; Burst’s safety system rejects the schedule.

Read-only array without attribute. If you read but never write to a NativeArray, mark it [ReadOnly]. Without it, Burst assumes you might write, which prevents safe parallel reads in some cases and pollutes profiler attributions.

The Fix

Step 1: Use Unity.Mathematics types.

using Unity.Burst;
using Unity.Collections;
using Unity.Jobs;
using Unity.Mathematics;

[BurstCompile]
public struct MoveJob : IJobParallelFor
{
    [ReadOnly]  public NativeArray<float3> velocities;
                public NativeArray<float3> positions;
    [ReadOnly]  public float deltaTime;

    public void Execute(int index)
    {
        positions[index] += velocities[index] * deltaTime;
    }
}

Step 2: Schedule with the right batch size.

var job = new MoveJob {
    velocities = velocityArray,
    positions = positionArray,
    deltaTime = Time.deltaTime,
};

JobHandle handle = job.Schedule(positionArray.Length, 64);
handle.Complete();

Batch size 64 is a sensible default. For very small jobs, use a higher batch size (256+) so the scheduling overhead does not dominate.

Step 3: Avoid managed APIs.

// BAD: Mathf in a Burst job
float distance = Mathf.Sqrt(dx*dx + dy*dy);

// GOOD: Unity.Mathematics
float distance = math.sqrt(dx*dx + dy*dy);

// BAD: Debug.Log inside Execute
Debug.Log("value");

// GOOD: Use Unity Logging or Burst-compatible logging only

Step 4: Use NativeDisableParallelForRestriction sparingly. If you know writes are safe (e.g., you spread workload by chunks), disable the restriction:

[NativeDisableParallelForRestriction]
public NativeArray<float> output;

Use only when you can prove no two threads write the same index. Otherwise data corruption is silent and platform-dependent.

Step 5: Inspect the Burst Inspector. Window → Analysis → Burst Inspector. Pick your job from the list. The right pane shows the assembly Burst produced (or a red error message). Errors here pinpoint the offending line, often a single managed call buried in a helper struct.

Common Burst Errors Cheat Sheet

BC1042: managed function pointer
       Cause:  delegate, virtual call, or interface dispatch
       Fix:    use FunctionPointer<T> or refactor to direct call

BC1059: managed method invocation
       Cause:  string, List, Mathf, Debug
       Fix:    replace with Unity.Mathematics / NativeArray

MJ0006: NativeArray in parallel-for
       Cause:  writing to index other than Execute’s index
       Fix:    add ReadOnly, or NativeDisableParallelForRestriction

Performance Note

Burst-compiled IJobParallelFor with batch size 64 typically runs 5–20x faster than equivalent main-thread code. The perf win disappears entirely if jobs have to wait on managed sync points. Schedule jobs early in the frame, complete late, and chain dependencies via JobHandle.CombineDependencies.

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

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

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

Diagnosing this class of bug benefits from a structured approach: confirm the symptom, isolate the variables, hypothesize the cause, and verify the hypothesis before writing fix code. Skipping the isolation step is the most common mistake; without it, fixes often address symptoms while the underlying cause continues to produce other variations.

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

Edge cases for this class of issue often involve specific timing: the first frame after a state change, the last frame before a transition, frames where multiple subsystems update simultaneously. Reproducing these reliably is part of what makes the bug class hard to test.

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.

“Burst speaks native, not managed. ReadOnly, WriteOnly, and Unity.Mathematics are the three keys to compile success.”

Related Issues

For DOTS issues with Burst, see DOTS Burst Managed Code Error. For Burst silently skipping jobs, see Burst Silently Skipping Job.

No managed types. ReadOnly attributes. Index-local writes. Burst is fast and strict.