Search Issue Tracker
Fixed
Fixed in 1.21.18, 2.0.3
Votes
1
Found in [Package]
1.21.9
Issue ID
ADDR-3358
Regression
Yes
Large memory usage when using BuildLayoutGenerationTask
Reproduction steps:
1. Open the attached “TestBuildLayoutGenerationTask” project
2. In the top menu select Tools > Build Addressables and observe the pop-up message
Expected result: The heap size used is small (around 0.1 GB)
Actual result: The heap size used is large (around 2.1 GB)
Reproducible with: 1.21.3 (2020.3.47f1), 1.21.9 (2020.3.47f1, 2021.3.22f1, 2022.2.15f1, 2023.1.0b12, 2023.2.0a10)
Not reproducible with: 1.21.2 (2020.3.47f1)
Note: For the reproduction to occur “Debug Build Layout” in Preferences > Addressables must be checked
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
- Crash on EnsureUniqueSiblingName when calling GameObjectUtility.EnsureUniqueNameForSibling() with a null argument
- Changes are not applied when selecting Platform settings for Plugins
- Particle System only collides with one Terrain Collider at a time when Collision Type is set to 'World'
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
Resolution Note (fix version 2.0.3):
Fixed in: Scriptable Build Pipeline 2.0.1
Resolution Note (fix version 1.21.18):
Fixed in: Scriptable Build Pipeline 1.21.20