Search Issue Tracker
By Design
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
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.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
Resolution Note:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.