Quick answer: Open Jobs > Burst > Open Inspector to see every job’s compilation status. If a job shows “Not Compiled” or “Error,” Burst dropped to mono silently. Remove managed types, switch to native containers, and enable Synchronous Compilation to catch errors at compile time.

Here is how to fix Unity Burst compiler silently skipping job. You add [BurstCompile] to a job, expecting 10x speedup. Profiler shows no improvement. You try a more complex operation — still no speedup. Burst is supposed to print warnings when compilation fails, but when the failure happens during background compilation, they are easy to miss. The job runs unoptimized and you do not know.

The Symptom

A job marked [BurstCompile] does not show the expected performance improvement:

What Causes This

Managed type references. Burst only handles value types. Using string, List<T>, class instances, or any managed reference type inside a job prevents Burst compilation. The job falls back to C# mono execution.

Exceptions. try/catch blocks and throw statements are not supported. Remove them or use Burst-safe error signaling (return flags, NativeArray for error counts).

Static fields. Accessing non-readonly static fields from Burst jobs is not allowed. Use SharedStatic<T> or pass values in via job fields.

Generic method calls. Some generic method calls cannot be Burst-compiled. Specialize them or use explicit type parameters.

Async compilation dropping errors. Burst compiles in the background by default. If a job fails to compile while your game is running, Burst may not print a visible error until the next domain reload.

The Fix

Step 1: Open the Burst Inspector. Window > Jobs > Burst > Open Inspector. This window lists every Burst-eligible method in your project with its compilation status:

Click a method to see the generated assembly (or the error). Errors explain what is incompatible.

Step 2: Enable Synchronous Compilation during development. Jobs > Burst > Synchronous Compilation. Now errors surface at compile time, not on first run. Slows down iteration but catches issues immediately.

Also enable Safety Checks and Leak Detection for further error detection in editor. Disable for builds.

Step 3: Replace managed types with native.

// Bad: List<T> is managed, breaks Burst
[BurstCompile]
public struct BadJob : IJob
{
    public List<float> values; // ERROR
    public void Execute() { // ... */ }
}

// Good: NativeArray is value-type-like
[BurstCompile]
public struct GoodJob : IJob
{
    public NativeArray<float> values;
    public void Execute()
    {
        for (int i = 0; i < values.Length; i++)
            values[i] *= 2f;
    }
}

NativeArray, NativeList, NativeHashMap, NativeQueue are all Burst-compatible. Remember to Dispose them when the job completes.

Step 4: Avoid exceptions inside jobs. Burst allows throw new ArgumentException in some cases but the general rule is no exception handling. Use assertion-style checks that terminate the job gracefully:

[BurstCompile]
public struct SafeJob : IJob
{
    public NativeArray<int> data;
    public void Execute()
    {
        if (data.Length == 0)
            return; // early exit, no exception

        // ... work on data ...
    }
}

Testing Burst Speedup

Compare with and without Burst by temporarily disabling. Jobs > Burst > Enable Compilation toggle off runs everything without Burst. Profile your scene; toggle back on and profile again. Real Burst acceleration typically shows 3–10x speedup on math-heavy workloads.

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

For shipping games, the safest verification is a staged rollout. Apply the fix to 1% of players for 24 hours; watch the affected metric; expand if green. Skipping the staged rollout means the verification is the entire player base, which is too high a stakes for most fixes.

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

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

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

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

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.

“Burst is silent when it fails. The Inspector is the only ground truth. Check it before trusting your performance numbers.”

Related Issues

For managed code errors, see Burst Compile Error Managed Code. For DOTS query issues, DOTS Entity Query Missing Tag Component covers related ECS patterns.

Burst Inspector is the truth. Synchronous Compilation surfaces errors. Native types only.