Porting Unity to CoreCLR | Unity Blog

I love this series where Unity engineers dive deep into details of the engine. The post slightly explains how memory allocation is managed by a garbage collector. Unity currently uses the Boehm GC, which is conservative and non-moving. In contrast, .NET CoreCLR employs a precise, moving garbage collector, which offers better performance. The Unity engine and editor code were initially developed based on the Boehm garbage collector's requirements. To use the CoreCLR GC, several modifications are required, including changes to custom marshaling tools used by Unity, such as the bindings generator and the proxy generator. Unity is gradually transitioning to the new representation of references to managed objects in the unmanaged code to ensure a GC-safety in the engine. This work will enable the use of the CoreCLR GC, which should improve performance and efficiency by minimizing the GC's involvement in native code. There are still no release dates tho

https://blog.unity.com/engine-platform/porting-unity-to-coreclr

#gc #coreclr