Search Issue Tracker
Fixed
Fixed in 2022.3.35f1, 6000.0.8f1
Votes
1
Found in
2022.3.30f1
6000.0.3f1
7000.0.0a1
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
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
Resolution Note (fix version 6000.0.8f1):
Ensure that destructors are called when using BatchAllocator