Search Issue Tracker
Won't Fix
Votes
2
Found in
2022.3.41f1
6000.0.14f1
6000.1.0a7
6000.2.0a1
Issue ID
UUM-77657
Regression
No
Massive memory spike when generating Prefab thumbnail. Can cause computer to crash.
How to reproduce:
1. Open the “IN-81932_memory“ project
2. Open the “prefab1“ asset
3. Select AutoSave in the top right corner of the Scene view
4. Open Task Manager on the device
5. Enable and disable the prefab in the Inspector 10-15 times
6. Observe the memory usage in the Task manager
Expected result: The memory stays stable
Actual result: The memory increases significantly
Reproducible with: 2021.3.42f1, 2022.3.41f1, 6000.0.14f1
Reproducible on: Windows 10, Windows 11
Not reproducible on: No other environment tested
Note:
- The issue does not reproduce after re-importing materials
- The project might open with errors regarding packages or prefabs. The issue is reproducible despite the errors.
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:
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.
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.