Search Issue Tracker
Fixed
Fixed in 2022.3.35f1, 6000.0.8f1
Votes
1
Found in
2022.3.30f1
6000.0.3f1
Issue ID
UUM-72458
Regression
No
Memory Leak when using InstantiateAsnyc to instantiate a large Prefab
How to reproduce:
1. Open the “IN-76682_repro“
2. Open the “SampleScene“
3. Enter Play Mode
4. Select the “Example“ GameObject
5. In the inspector enable “Async Instantiate“
6. Observe the Console
Expected result: The memory keeps increasing
Actual result: The memory stays around the same
Reproducible with: 2022.3.30f1, 6000.0.3f1
Could not test with: 2021.3.38f1
Reproducible on: Windows 10
Not reproducible on: No other environment tested
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 (fix version 6000.0.8f1):
Ensure that destructors are called when using BatchAllocator