Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X, 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
Votes
0
Found in
2021.3.49f1
2022.3.60f1
6000.0.42f1
6000.1.0b10
6000.2.0a6
6000.3.0a1
6000.4.0a1
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
- Can’t delete gradient keys with Mac keyboard or context menu options
- Editor freezes for a few minutes when closing or switching a VFX window that was opened in a previous project
- UI Overlaps when switching Render Pipeline Asset for different Quality Levels in Quality Project Settings
- Ray Tracing Shader link to the documentation isn’t working
- Warning "BatchRendererGroups currently don't support override shaders" is spammed in Play mode when using H-Trace WSGI with BatchRenderGroups
Add comment