Search Issue Tracker
Active
Votes
0
Found in
1.23.1
2.3.16
Issue ID
UUM-100347
Regression
No
Memory leak in ContentBuildInterface.GetTypeForObjects when building addressables
How to reproduce:
1. Open the attached “IN-95489_Addressables_memory.zip” project
2. Open the Addressables Groups window (Asset Management > Addressables > Groups)
3. Select the “Water” Addressables Group
4. Run an Addressables build by pressing Build > New Build > Default Build Script
5. Observe the Editor memory usage in Task Manager
Expected result: Memory usage is stable throughout the build process and does not scale with number of textures
Actual result: Memory usage spikes and scales linearly with the amount of textures, reaching up to 14gb at times
Reproducible in: 1.23.1 (2021.3.49f1, 2022.3.59f1), 2.3.16 (6000.0.41f1, 6000.1.0b9, 6000.2.0a6)
Reproducible on: Windows 10, Windows 11
Not reproducible on: No other environments tested
Note: The editor may OOM crash with a high enough number of textures
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment