Search Issue Tracker
Fixed
Votes
1
Found in
2020.2.2f1
2020.3
2021.2
Issue ID
1310007
Regression
No
Editor memory usage significantly increases while building when Resources folder contains large Sprite Atlases
GBReproduction steps:
1. Download and open the reproduction project from the provided link
2. Open the Task Manager
3. Build the project and investigate the memory usage while building
Expected result: Memory usage slightly increases
Actual result: Memory usage increases up to 11GB
Reproducible with: 2020.3.3f1, 2021.1.2f1, 2021.2.0a12
Could not test on: 2018.4, 2019.4 (asset bundle size is too large)
Reproducible with platforms:
Windows (up to ~8GB)
Android (up to ~11GB)
macOS (up to ~8GB)
iOS (up to ~9GB)
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:
Unable to reproduce in latest 2019.4, 2020.3, 2021.1, 2021.2 versions