Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
1
Found in
2023.2.13f1
Issue ID
UUM-68159
Regression
Yes
Memory Leak warnings are thrown when opening an imported Prefab
Reproduction steps:
1. Create a new project with “3D (URP)” template
2. Import the "Repro” package
3. Open the “Assets/Prefabs/Gameplay/Units/BlueKing.prefab” Prefab
4. Observe the Console window
Expected result: No warnings are thrown in the Console window
Actual result: “[Worker0] Internal: There are remaining Allocations on the JobTempAlloc. This is a leak, and will impact performance” warning is thrown
Reproducible with: 2022.2.0a15, 2022.2.20f1, 2023.2.13f1
Not reproducible with: 2021.3.35f1, 2022.2.0a14, 2022.3.20f1
Fixed in: 2022.2.21f1, 2023.3.0a2
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Note: Not reproducible when opening the prefab after reopening the project
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
2023.2 is not maintained - please reopen the bug if this happens in Unity 6 or any other long term support versions
Resolution Note (2023.2.X):
2023.2 is not maintained - please reopen the bug if this happens in Unity 6 or any other long term support versions