Bug There are remaining Allocations on the JobTempAlloc. This is a leak...

So I'm getting this on two prefabs in particular:

Any ideas on how to eliminate this issue so I can continue to work without out of memory issues?

 

same issue... 2022.2.12

 

Same here. My console is constantly getting flooded with these after updating from 2021 to 2022.

 

I rolled back to 2021. Then scrapped entire project and started again because my code was an absolute mess.

 

x2

 

I get also the same messages in Console in version 2022.3.0 LTS (actually I got this messages for all versions 2022). There are 4 messages (see the picture). Later I see that my FPS start droping in my Game and it became slower and slower and I must restart the Unity.

 

This is happening to me too. Just updated the project to 2022.3.1f1.
Getting the warning people reported above related to "Internal: deleting an allocation that is older than its permitted lifetime of 4 frames (age = 6)".

It goes away if I turn off our runtime navmesh build which calls NavMeshSurface.UpdateNavMesh(NavMeshData)
... which our game requires to react to runtime changes.

Its happening in one other spot I havnt tracked down yet either, but the above navmesh one was 100% reproducible in the project.

I am investigating this because I have user reports that the app is hard crashing for them when this section of code is being called and since its unity code I am looking at updates to fix it... so they may be related, but I cant seem to do anything about it currently.

 

Do we already have a solution for this?

 

Same problem in 2023.1

This one occurred just after opening one of the Cinemachine example scenes.

The problem only seems to happen when I click items in the project window. It does NOT seem to happen if I close the Inspector tab, only when I click various items in the Project tab and cause the Inspector contents to change.

 

Same problem here (version 2022.3.2f1). It started happening when I added a partical System into a prefab. Not saying it has anything to do with prefab or partical system, just noticed that it started to give leak warnings when I first worked with it. Never had this warning before.
I don't have Cinemachine in this Project

 

same errors when I switch to 2022.2.12, the problem with sending a bug report is that fails too. it appears to impacting various items.

 

I get this callstack after enabling validation:

Code (CSharp):

1. [Worker0] Allocation of 32 bytes at e020c760 in block 0 (frameIndex=1, lifetime=4, age=2, state=OK)
2. 0x00007ff72a26f9eb (Unity) PlayableGraph::DestroyPlayableDeferred
3. 0x00007ff72a6f6821 (Unity) Animator::ClearInternalControllerPlayable
4. 0x00007ff72a6f6a39 (Unity) Animator::ClearObject
5. 0x00007ff72a6f7abf (Unity) Animator::Deactivate
6. 0x00007ff729c25835 (Unity) GameObject::ActivateAwakeRecursivelyInternal
7. 0x00007ff729c25674 (Unity) GameObject::ActivateAwakeRecursivelyInternal
8. 0x00007ff729c253f9 (Unity) GameObject::ActivateAwakeRecursively
9. 0x00007ff729c28629 (Unity) GameObject::Deactivate
10. 0x00007ff729fdeb90 (Unity) UnityScene::OnGameObjectChangedScene
11. 0x00007ff72a1f10fd (Unity) SceneManagerBindings::MoveGameObjectToScene
12. 0x00007ff7293dfba1 (Unity) SceneManager_CUSTOM_MoveGameObjectToScene_Injected
13. 0x000002722f69b4e5 (Mono JIT Code) (wrapper managed-to-native) UnityEngine.SceneManagement.SceneManager:MoveGameObjectToScene_Injected (UnityEngine.GameObject,UnityEngine.SceneManagement.Scene&)
14. 0x000002722f69b40b (Mono JIT Code) UnityEngine.SceneManagement.SceneManager:MoveGameObjectToScene (UnityEngine.GameObject,UnityEngine.SceneManagement.Scene)
15. 0x00000274724ffe03 (Mono JIT Code) UnityEditor.PreviewScene:AddManagedGO (UnityEngine.GameObject)
16. 0x000002722f69ffc3 (Mono JIT Code) UnityEditor.PreviewRenderUtility:AddManagedGO (UnityEngine.GameObject)
17. 0x000002722f69d9c3 (Mono JIT Code) UnityEditor.GameObjectInspector/PreviewData:UpdateGameObject (UnityEngine.Object)
18. 0x000002722f6999db (Mono JIT Code) UnityEditor.GameObjectInspector/PreviewData:.ctor (UnityEngine.Object,bool)
19. 0x000002722f699283 (Mono JIT Code) UnityEditor.GameObjectInspector:GetPreviewData (bool)
20. 0x000002722f698d4b (Mono JIT Code) UnityEditor.GameObjectInspector:RenderStaticPreview (string,UnityEngine.Object[],int,int)

Unity devs please elaborate. I'm in the middle of transferring a large project from 2020 to 2022 and now in doubts. How severe is it?
2022.3.4f1

 

Hi, following this tutorial https://learn.unity.com/tutorial/lesson-2-4-collision-decisions
I saw the problem coming when changing from 2021 to 2022.3.4f1

At the beginning I got some warning about the mesh of the assets, something about not being valid FBX, What I am thinking is that FBX changed to be stricter and then without validation of the mesh as required in 2022, could trigger the memory leak because another error related to this?

Probably I am wrong, but I am seeing a lot of FBX warnings from old assets when loading them in 2022 but no problem in 2021 or 2020

 

Has there been updates on this error? I am getting it while following this tutorial: https://learn.unity.com/tutorial/sp...66dbedbc2a0021b1bc7c#5c7f8528edbc2a002053b3f5
version 2022.3.7

 

I'm in the exacte same case, I need to use NavMeshSurface.UpdateNavMesh(NavMeshData) but if I do then I got thos warning... Did you find a solution about that ?

 

Unity 2023.1.7f1. directly after calling
GameObject curPrefab = PrefabUtility.LoadPrefabContents(prefabPath);
PrefabUtility.SaveAsPrefabAsset(curPrefab, prefabPath);
PrefabUtility.UnloadPrefabContents(curPrefab);

one time.

 

Getting the same error after upgrading to Unity 2022.3.7f1 from 2021. In our case, we just need to open Animator tab for a few prefabs, and on 4th or 5th prefab the error will show up. After that sometimes the editor won't even show Animator state machine and will start throwing "Null reference exception" errors.

NullReferenceException: Object reference not set to an instance of an object

UnityEditor.Graphs.Edge.WakeUp () (at <021ad9261da248d7a1251390c25c529f>:0)

UnityEditor.Graphs.Graph.DoWakeUpEdges (System.Collections.Generic.List`1[T] inEdges, System.Collections.Generic.List`1[T] ok, System.Collections.Generic.List`1[T] error, System.Boolean inEdgesUsedToBeValid) (at <021ad9261da248d7a1251390c25c529f>:0)

UnityEditor.Graphs.Graph.WakeUpEdges (System.Boolean clearSlotEdges) (at <021ad9261da248d7a1251390c25c529f>:0)

UnityEditor.Graphs.Graph.WakeUp (System.Boolean force) (at <021ad9261da248d7a1251390c25c529f>:0)

UnityEditor.Graphs.Graph.WakeUp () (at <021ad9261da248d7a1251390c25c529f>:0)

UnityEditor.Graphs.Graph.OnEnable () (at <021ad9261da248d7a1251390c25c529f>:0)

In addition, after getting this bug, using "build and run" and testing on the device some sprites don't show up. Closing Unity and re-building before the error results in a proper build without the issue with the missing sprites. So it seems this leak affects the builds too, not only the editor console.
We can't roll back to Unity 2021 unfortunately, so hoping this will be fixed soon.

 

Guys --- Does this have a bug ticket raised as its happening in 2023.1.

The code culprit its happening for me is this

var modelRootGO = (GameObject)AssetDatabase.LoadMainAssetAtPath(assetPath);

var instanceRoot = PrefabUtility.InstantiatePrefab(modelRootGO) as GameObject;

Soon as the prefab variant is created and i click on it in the project window it comes up with

 

I just filed a bug report under
CASE IN-56259

 

I gave up on this years ago. Best you can hope for is "unable to reproduce".

 

Maybe if they spend more time on their engine solving real issues like this they might improve their monitization issues another way.

 

Yeah... I've no idea how management didn't see this coming. But we live in a time of degeneration. Everything gets worse.

 

How do you change that? The pic isn't loading.

The reply from above was deleted, anyhow, I got the bug as well

 

Can you give a link to this ticket? Search there doesn't find it by the number.

 

I have that same problem. It started to appear when we moved from 2019 to 2022.

 

still occurs in 23.1.18f1

 

Can you please re-raise the issue ticket for this? Seems like the ticket i raised can't be traced.

 

Not sure if it helps anyone, but I was experiencing the same issue and updating to a newer version of unity as stated here https://issuetracker.unity3d.com/is...ntroller-to-an-animator-component-of-a-prefab fixed the problem.

 

nope, still happens in 2022.3.15
seems it has something to do with ScriptableObject...

 

Done, IN-67428
I think I accidentally send the bug report twice, another one is IN-67423
It should contains the entire project. It's just a tutorial project I followed (Code Monkey's Kitchen Chaos single player tutorial) so doesn't contain any sensitive information.
With all the assets it should be very easy to recreate this problem.

 

i have the same problem unity ver 2022.3.6f1 LTS .i create a new project to test thing and a empty game object and as soon as i put it into prefab the warning show up the only thing that i did is to install navigation AI .did a terrain and bake it

 

i will revert back to ver 2019 i had enoph bug already