Search Issue Tracker
Fixed
Fixed in 2022.3.8f1, 2023.1.9f1, 2023.2.0a1
Votes
5
Found in
2022.2.16f1
2023.1.0b13
2023.2.0a11
2023.3.0a3
Issue ID
UUM-33327
Regression
Yes
Memory leak warning shows up in the Console when adding an Animator Controller to an "Animator" Component of a prefab
How to reproduce:
1. Open the attached project “Test.zip“
2. Select the “Cube“ prefab
3. Disable and re-enable the “Animator“ Component
Expected result: There is no leak warning in the Console
Actual result: “[Worker0] Internal: There are remaining Allocations on the JobTempAlloc. This is a leak, and will impact performance“ warning in the Console
Reproducible with: 2022.2.0a14, 2022.2.16f1, 2023.1.0b13, 2023.2.0a11
Not reproducible with: 2020.3.47f1, 2021.3.23f1, 2022.2.0a13
Reproduced on: macOS 13.0.1 (Intel), Windows 11 (by reporter)
Note: Might need to create and attach a new Animator Controller to the “Animator” Component of the prefab to reproduce the issue
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Rendering locks up when not looking at a transparent material on Meta Quest 2
- Volumetrics break when using a Custom Pass to create a Thickness Buffer for Alpha Clipping
- All tests are run instead of only the failed ones when the "Rerun Failed" button is pressed
- GameObject is not masked when the "Render PostProcessing Effects" pass executes with a resolved non-MSAA Color target and MSAA DepthStencil target
- [Android] Gfx.WaitForGfxCommandsFromMainThread high performance usage and inconsistency when built Player scene has Canvas GameObject on a specific Project
horeaper
Jan 25, 2024 11:01
not fixed, still happens in 2022.3.15
rodriguezeidner
Sep 30, 2023 01:01
Something similar happening here, I'm using a scriptable object to contain an Animator Controller and a object with a script to change the animator controller in game depending on the chosen scriptable object, and since I added that there's a memory leak.