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
- NullReferenceException is thrown when pressing the "Enter" key to select an item in a ListView
- Burst internal compiler errors are thrown when creating a new 2D project
- Tile Paint action disappears from Undo History when Tile Selection tool has been used beforehand
- The pregenerated LightDefinition.cs.hlsl does not match the source LightDefinition.cs when regenerating shader includes
- Crash on GizmoDrawingPhysics2D::DrawCompositeCollider2DGizmo when opening a Scene that has corrupted GameObjects with Tilemap Components
Resolution Note (fix version 2020.1):
Fixed by Editor Version: 2020.1.0a16