Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2017.4.X
Votes
0
Found in
2018.1.0b6
Issue ID
1030584
Regression
No
Unity crashes while packing a huge sprite with sprite atlas when the graphics API is set to D3D11 or D3D12
How to reproduce:
1. Open the attached Unity project.
2. Open the sprite atlas named "CrashAtlas" in the Inspector window.
3. Press "Pack Preview".
4. Wait till sprite packing is finished.
Expected result: sprite atlas successfully packs the sprites.
Actual result: a message appears stating that Unity could not allocate memory. After closing the message, Unity crashes.
Reproducible with - 2017.1.0b5, 2017.1.3p4, 2017.2.2p4, 2017.4.2f2, 2018.1.0f2, 2018.2.0b3
Could not test with - 5.6.0a1, 5.6.6f2, 2017.1.0b4 (Sprite Atlas first introduced in 2017.1.0b5)
Note:
The crash happens when the sprite's max size is set to 4096 or 8192, sprite mode is multiple and there is a lot of sprites in it.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- A submenu disappears on MacOS when the MenuItem method argument "isVariableFunction" is set to "false" and priority argument is set to "-1"
- The Sprite Library Editor window has an incorrect order of Sprites when the Sprites are reordered and the order saved
- Tilemap Tiles do not get lit up unless the Light Range is greater than the distance between the position of the Tile before the transformation and the Light Source when the Tile is transformed with Tilemap.SetTransformMatrix method
- The Editor and "Reloading Domain" windows are frozen when entering Play Mode
- Crash when attempting to create a custom FMOD DSP unit
Add comment