wave4-native-disable-container-safety-restriction

To use per-worker scratch NativeContainers in Unity DOTS without safety errors, apply the [NativeDisableContainerSafetyRestriction] attribute to the container and enforce strict per-worker ownership semantics.

Your IJobChunk parallel job fails DOTS safety checks because the system detects a shared container ownership risk. You must opt out of safety restrictions by relying on job-struct copy-per-dispatch guarantees.

The best way to allocate a NativePriorityHeap for each parallel worker is using the IJobChunk pattern, where job-struct copy semantics ensure each worker receives its own isolated scratch container instance.

You should not use NativeDisableContainerSafetyRestriction when your job logic cannot guarantee per-worker container ownership, as bypassing safety checks can introduce silent race conditions across workers.

Yes, IJobChunk guarantees separate container instances for each parallel worker during execution because its job-struct copy-per-dispatch mechanism ensures no shared container ownership occurs across workers.

Yes, you can disable Unity DOTS container safety restrictions for performance optimization in Burst by opting out of shared-container safety, provided you manually enforce per-worker ownership semantics.