Search Issue Tracker
Won't Fix
Votes
0
Found in
2023.1.11f1
2023.2.0b7
Issue ID
UUM-47648
Regression
Yes
Memory leak warning appears in the console when deactivating/activating a GameObject
Reproduction steps:
1. Open the attached project “PrefabLeak”
2. Double click on prefab ”Assets/Models/Units/Goblin/Goblin_01.prefab”
3. Select the “goblin_shield” GameObject
4. Deactivate and activate the selected GameObject
5. Observe the Console
Expected result: No errors in the console
Actual result: “There are remaining Allocations on the JobTempAlloc. This is a leak, and will impact performance” error is printed
Reproducible with: 2023.1.10f1, 2023.1.11f1, 2023.2.0b7
Not reproducible with: 2021.3.30f1, 2022.3.8f1, 2023.1.9f1
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Notes:
- If no warnings appeared after the reproduction steps, then reimporting all assets and following the steps should make the warning appear
- The issue can be reproduced once or twice, afterwards, the warning appears inconsistently (unless assets are reimported)
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
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
- Editor crashes on D3D12GetInterface when repeatedly enabling and disabling 256 text components
- Flickering bright white dots in the Scene when the Android Platform is selected and DX11 Graphics API is used with Iris(R) Xe Graphics GPU
- Inconsistent capitalization and misaligned text in multiple query blocks in Search window
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.