Feedback Job system Manual Allocator.Temp needs revising

• https://docs.unity3d.com/Manual/JobSystemNativeContainer.html
• 
  
• Allocator.Temp has the fastest allocation. It is for allocations with a lifespan of one frame or fewer. You should not pass NativeContainer allocations using Temp to jobs. You also need to call the Dispose method before you return from the method call (such as MonoBehaviour.Update, or any other callback from native to managed code).

Everything I have read on this forum is that Allocator.Temp is always a No-op and just creates useless overhead. The job system Manual seems to say otherwise. Is it only a No-op with Burst? I think the documentation should be revised.

 

In all honesty, I've never heard Allocator.Temp create overhead. Did I miss something? The only thing I've heard is that Temp is the fastest allocation type, and my guess is that a preallocated linear allocator is used here, in which the pointer is reset every frame and Dispose() is ignored.

 

I think @TheOtherMonarch is talking only about the Dispose call not being required and generating overhead.
Afaik not disposing Temp memory doesn't produce actual leaks but eg allocations in a loop sum up whereas they do not when Disposing them.

 

Based off this thread,
https://forum.unity.com/threads/allocator-temp-container-need-dispose.852082/#post-5619760
I thought dispose on Temp was a no-op

s_schoener
Freeing Temp memory is a no-op. For jobs, it is automatically released once the job finishes. It is still a good idea to not allocate temp memory for every single iteration of an IJobParallelFor since you can exhaust the Temp allocator.

s_schoener
No, there is no need to dispose them. It's a no-op.

 

Dispose of Temp memory is a no-op on the native side.
It's just wrong documentation which will be fixed.