Should Burst Safety Checks be on in shipping build?

No. Project Settings → Burst AOT → Disable Safety Checks. Editor leaves On for development; player ships with checks off for performance.

Editor checks: bounds, alias, race conditions. Helpful debugging. Production: undefined behavior on misuse but 2-5x faster job execution.

Catching production bugs?

Test thoroughly in Editor with checks on. Run development player builds for a week before shipping with checks off. Race conditions surface in Editor.

Fix: Burst Safety Checks Slow Player Build

Quick answer: Project Settings → Burst AOT → Disable Safety Checks in player builds. Keep On in Editor.

Profiler shows Burst job 30% slower in player vs editor. Safety checks shouldn't ship.

The Fix

Project Settings → Burst AOT Settings:
  Disable Safety Checks:    true
  Disable Burst Compilation: false
  Use Native Compiler:       true

Edit → Burst → Safety Checks: true      // editor only

Builds run with checks off; editor keeps them on. Best of both worlds.

Verifying

Build player. Profile job time. Compared to checks-on baseline: 2-3x faster on the same job. Editor: same speed as before.

“Off in player. On in editor. Best of both.”

Related Issues

For Burst AVX target, see AVX. For Burst AOT PDB, see AOT PDB.

Off in player. Faster.