Unity 2022.3.0, Entities 1.0.10: Leaks Detected - even in a new, mostly empty project?

[WeekendWarrior]

Hello guys,

I upgraded my project to the new Unity LTS version and the new entities package and all of the sudden I constantly get a console message that tells me that Unity detects a varying amount of leaks/persistent indiviual allocations.

So I went to Edit->Preferences->Jobs->Leak Detection Level, set it to “Enabled With Stack Trace” and tried to figure out at which point I made a mistake by going through the callstack in the “found x leak(s) from callstack” messages. Unfortunately, I never got to any of my scripts, just a series of Unity scripts calling each other.

Next I tried to remove as many objects and subscenes as possible to narrow down what causes the problem but the leaks wouldnt disapper. Thus, I decided to create a new project instead and add stuff until the leaks show up again, which, unfortunately, happened almost immediately. Here’s what I did:

1. Create a new project (using the 3D URP template)
2. Import the Entities Graphics package (which auto imports a some other DOTS packages)
3. Add a subscene to sample scene.
4. Add a 3d Object (Cube) to the subscene

And - upon entering and leaving play mode - the leaks are back! This isnt supposed to happen, right?

A typical “found leak” message looks like this:

Found 2 leak(s) from callstack:
0x0000021ab9f131c3 (Mono JIT Code) Unity.Collections.Memory/Unmanaged/Array:Resize (void*,long,long,Unity.Collections.AllocatorManager/AllocatorHandle,long,int) (at ./Library/PackageCache/com.unity.collections@2.1.4/Unity.Collections/Memory.cs:79)
0x0000021ab9f13063 (Mono JIT Code) Unity.Collections.Memory/Unmanaged:Allocate (long,int,Unity.Collections.AllocatorManager/AllocatorHandle) (at ./Library/PackageCache/com.unity.collections@2.1.4/Unity.Collections/Memory.cs:20)
0x0000021bdd91595b (Mono JIT Code) Unity.Entities.EntityQueryImpl:Allocate () (at ./Library/PackageCache/com.unity.entities@1.0.10/Unity.Entities/Iterators/EntityQuery.cs:1968)
0x0000021bdd9157fb (Mono JIT Code) Unity.Entities.EntityQuery:Construct (Unity.Entities.EntityQueryData*,Unity.Entities.EntityDataAccess*) (at ./Library/PackageCache/com.unity.entities@1.0.10/Unity.Entities/Iterators/EntityQuery.cs:2148)
0x0000021bdd911823 (Mono JIT Code) Unity.Entities.EntityQueryManager:CreateEntityQuery (Unity.Entities.EntityDataAccess*,Unity.Entities.ArchetypeQuery*,int,Unity.Entities.ComponentType*,int) (at ./Library/PackageCache/com.unity.entities@1.0.10/Unity.Entities/Iterators/EntityQueryManager.cs:720)
0x0000021bdd90ab53 (Mono JIT Code) Unity.Entities.EntityQueryManager:CreateEntityQuery (Unity.Entities.EntityDataAccess*,Unity.Entities.EntityQueryBuilder) (at ./Library/PackageCache/com.unity.entities@1.0.10/Unity.Entities/Iterators/EntityQueryManager.cs:536)
0x0000021bdd93896b (Mono JIT Code) Unity.Entities.EntityManager:CreateEntityQueryUnowned (Unity.Entities.EntityQueryBuilder&) (at ./Library/PackageCache/com.unity.entities@1.0.10/Unity.Entities/EntityManager.cs:4243)
0x0000021bdd95e8b3 (Mono JIT Code) Unity.Entities.EntityManager:CreateEntityQuery (Unity.Entities.EntityQueryBuilder&) (at ./Library/PackageCache/com.unity.entities@1.0.10/Unity.Entities/EntityManager.cs:4237)
0x0000021be16f3c0b (Mono JIT Code) Unity.Entities.EntityManager:CreateEntityQuery (Unity.Entities.EntityQueryDesc[ ]) (at ./Library/PackageCache/com.unity.entities@1.0.10/Unity.Entities/EntityManager.cs:4225)
0x0000021be1755103 (Mono JIT Code) Unity.Entities.BakingCompanionComponentSystem:UpdateCompanionQuery () (at ./Library/PackageCache/com.unity.entities@1.0.10/Unity.Entities.Hybrid/Baking/BakingCompanionComponentSystem.cs:248)
0x0000021be1752b83 (Mono JIT Code) Unity.Entities.BakingCompanionComponentSystem:CreateCompanionGameObjects () (at ./Library/PackageCache/com.unity.entities@1.0.10/Unity.Entities.Hybrid/Baking/BakingCompanionComponentSystem.cs:81)
0x0000021be17526bb (Mono JIT Code) Unity.Entities.BakingCompanionComponentSystem:OnUpdate () (at ./Library/PackageCache/com.unity.entities@1.0.10/Unity.Entities.Hybrid/Baking/BakingCompanionComponentSystem.cs:222)
0x0000021be16d8243 (Mono JIT Code) Unity.Entities.SystemBase:Update () (at ./Library/PackageCache/com.unity.entities@1.0.10/Unity.Entities/SystemBase.cs:420)
0x0000021be174f2fc (Mono JIT Code) Unity.Entities.BakingUtility:postprocessBake (Unity.Entities.World,Unity.Entities.BakingSettings,Unity.Entities.BakingSystem) (at ./Library/PackageCache/com.unity.entities@1.0.10/Unity.Entities.Hybrid/Baking/BakingUtility.cs:170)
0x0000021be17042ab (Mono JIT Code) Unity.Entities.BakingUtility:BakeScene (Unity.Entities.World,UnityEngine.SceneManagement.Scene,Unity.Entities.BakingSettings,bool,Unity.Entities.IncrementalBakingChangeTracker) (at ./Library/PackageCache/com.unity.entities@1.0.10/Unity.Entities.Hybrid/Baking/BakingUtility.cs:87)
0x0000021be1702deb (Mono JIT Code) Unity.Scenes.Editor.LiveConversionDiffGenerator:Bake (Unity.Entities.BakingUtility/BakingFlags) (at ./Library/PackageCache/com.unity.entities@1.0.10/Unity.Scenes.Editor/LiveConversion/LiveConversionDiffGenerator.cs:214)
0x0000021be16f2313 (Mono JIT Code) Unity.Scenes.Editor.LiveConversionDiffGenerator:UpdateLiveConversion (UnityEngine.SceneManagement.Scene,Unity.Entities.Hash128,Unity.Scenes.Editor.LiveConversionDiffGenerator&,Unity.Scenes.LiveConversionMode,ulong,UnityEditor.GUID,Unity.Entities.Build.IEntitiesPlayerSettings,Unity.Scenes.LiveConversionChangeSet&

[FaithlessOne]

A developer of Netcode for Entities confirmed that there a still memory leaks within the ECS packages, so at least they know about and may take care about it in the future.

[Arnold_2013]

There have been more reports of leaks, I think the leak detection has become better. It did find a leak in my own code that was not found in previous versions. But I also get leak notifications from unity code.

When looking at the memory consumption of my application I don’t see the memory exploding, so as long as people have enough RAM it does not look like a real problem. Garbage collection hits performance harder than a memory leak, right . I am hopeful they will fix it.

From URP14.0.7 ForwardLights.cs :

2022.3 LTS leak detected in jobs?

Hello, I just updated to 2022.3, and for some reason it’s alerting me of a leak. I thought it had to do with my code, but when I enabled full stack traces I realized it has to do with lighting. I have no idea how to fix this, as it is part of URP. Any ideas? I’ll leave the details attached here: ./Library/PackageCache/com.unity.render-pipelines.universal@14.0.7/Runtime/ForwardLights.cs:137) 0x000001837ae08dc3 (Mono JIT Code) UnityEngine.Rendering.Universal.UniversalRenderer:.ctor (UnityEngi…

general ‘persistent allocates X individual allocations’ :

Leak Detection Menu is not appearing under jobs in Unity 2022.2 Beta

Hi there Im using Job System heavily without entities, and I'm seeing this error A Native Collection has not been disposed, resulting in a memory leak. Enable Full StackTraces to get more details. How do I enable full stack trace? There is no Leak Detection Menu under Jobs Please Advise

looked to me like this could be in user code:

Leak Detected : Persistent allocates 41 individual allocations.

Hello, i followed the turbomakesgames tutorial Leak Detected : Persistent allocates 41 individual allocations. i get leaks: (only posted the first one) Found 1 leak(s) from callstack: 0x00007ffdef4b57ef (1927aa1165b3ede9eaa66390321407e) SpawnAsteroidSystem::SpawnAsteroidSystem.OnUpdate (at C:/Users/hazzel/Unity Projects/dotsHelpMeJessus/Assets/Scripts/Systems/SpawnAsteroidSystem.cs:50) 0x00007ffdef4b487f (1927aa1165b3ede9eaa66390321407e) edae3ecf9518a834e7286f44182dc0c3 0x00007ffdef47a…

[Laicasaane]

@""

// this code will not trigger safety check because i use fixed size
NativeList<float3> pos = new NativeList<float3>(10, Allocator.Persistent)

The first argument is the initial capacity. When you use NativeList.Add it will increase the size of the list when there is no empty slot left.
https://docs.unity3d.com/Packages/com.unity.collections@2.2/api/Unity.Collections.NativeList-1.html#Unity_Collections_NativeList_1_Add__0__

Remarks
Length is incremented by 1. If necessary, the capacity is increased.

[Laicasaane]

@""

that’s true, but if I set the capacity to 0, it still triggers a safety check, so there must be at least 1 element in the nativelist if you don’t want to trigger a safety check.

That’s interesting. Maybe I should spend some time read the NativeList source code.

[Kyrieyf]

After importing the package，u can try to disable Unity’s Domain Reload setting. To do this, go to Edit > Project Settings > Editor menu, and enable the Enter Play Mode Options setting, but leave the Reload Domain and Reload Scene boxes disabled.