【Understanding the managed heap】
1、common problem faced by many Unity developers is the unexpected expansion of the managed heap。
2、The “managed heap” is a section of memory that is automatically managed by the memory manager of a Project’s scripting runtime (Mono or IL2CPP).
managed heap 由 Mono、IL2CPP 的 memory manager 自动管理。
3、Crucially, Unity’s garbage collection – which uses the Boehm GC algorithm – is non-generational and non-compacting. “Non-generational” means that the GC must sweep through the entire heap when performing a collection pass, and its performance therefore degrades as the heap expands. “Non-compacting” means that objects in memory are not relocated in order to close gaps between objects.
Unity's garbage collection 不会使用 relocate 来缓解 fragmentation 问题。
4、if a large object is allocated and there is insufficient contiguous free space to accommodate the object, as illustrated above, the Unity memory manager performs two operations.
First, if it has not already done so, the garbage collector runs. This attempts to free up enough space to fulfill the allocation request.
Second, If, after the GC runs, there is still not enough contiguous space to fit the requested amount of memory, the heap must expand. The specific amount that the heap expands is platform-dependent; however, most Unity platforms double the size of the managed heap.
5、
6、
7、
8、
参考：
1、https://docs.unity3d.com/Manual/BestPracticeUnderstandingPerformanceInUnity4-1.html