`UnsafeUtility.Malloc` uses Unity's allocators under the hood, for large persistent allocations this ultimately ends up calling the platform specific memory allocation function (`VirtualAlloc` on Windows).

Our allocators work on a Reserve + Commit system where memory is reserved but cannot be accessed, it is then committed when it is intended to be used and uncommitted when memory is freed (allowing for reuse). Due to various factors (mainly for allocation headers, page granularity & alignment); for larger allocations, our allocator tends to reserve more memory than requested.

With the above in mind, we have chosen to close this issue as "won't fix" as the cause is a combination of the specific processor's cache size, non linear access pattern (due to IJobFor multithreaded access) and the fact our allocator tends to allocate additional memory (leading to reaching cache size sooner).