Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2019.2
2019.3
2019.3.0b9
2020.1
Issue ID
1200814
Regression
No
Memory usage keeps growing indefinitely when building Sprite Atlases
Reproduction steps:
1. Open "1200814" project
2. Open the "Task Manager" -> "Details" -> Right-click Column name bar -> "Select columns" -> Check on "Commit Size"
3. Build a Standalone Player
4. Notice that when the Variants start building memory usage gets dramatically increased
Expected Result: Memory usage stays to a reasonable amount
Actual Result: Memory usage keeps growing indefinitely
Reproduced with(Max Commit Size): 2020.1.0a15(16GB), 2019.3.0f2(16GB), 2019.3.0b11(16GB), 2019.2.16f1(8Gb)
Did not reproduce on: 2018.4.14f1(5Gb)
Could not reproduce on: 2017.4.35f1(Packing Error)
-
spacefrog
Mar 09, 2020 10:59
I just updated to 2019.3.4F1 ( from 2019.2.21F1 )
While on 2019.2 i was able to work around the increasing memory requirements for atlas building by increasing my swapfile size , this does'nt work any longer on 2019.3.4F1
We have some big multipage altasses to bake and this bug alone hinders us to upgrade our project to 2019.3.4F1 from 2019.2 ( which now will not get any updates any longer )
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2020.1):
Fixed by Editor Version: 2020.1.0a16