Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2018.4.X, 2019.1.X
Votes
0
Found in
2018.3.0a1
2018.3.1f1
2019.1.0a1
2019.2.0a1
Issue ID
1121583
Regression
No
Crash in FitBlockMaskInBlockMaskUsingPadding when packing a Sprite Atlas with blockOffset value set to 0
How to reproduce:
1. Open user-submitted project (AtlasBlockOffsetCrash)
2. Navigate to Edit > Project Settings > Editor tab and set Sprite Packer Mode to 'Always Enabled'
3. In the Menu bar select Repro > Crash to pack a Sprite Atlas
Expected result: the Editor doesn't crash
Actual result: the Editor crashes
Reproducible with: 2018.3.3f1, 2019.1.0b1, 2019.2.0a3
Could not test with: 2017.4.19f1(SpriteAtlasPackingSettings namespace not yet implemented)
-
Daryl_1
Jun 09, 2019 21:30
Ignore above ^
Reproduced the issues by instantiating a SpriteAtlasPackingSettings and setting the atlas, without setting padding in the settings. -
Daryl_1
Jun 09, 2019 21:21
Please backport this fix to the LTS (2018.4)
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
- [macOS] There is no way to tell if you are running under Rosetta
- [AssetImport] Changing Graphics APIs in Android platform reimports most of the assets (textures, fonts, ...)
- Stack frames are missing from Console window when in Full Stack trace mode
- An error is returned and no package is listed if an invalid package is hosted on a scoped registry
- Crash with ComputeTileMeshJob when generating Navmesh
Resolution Note (fix version 2018.4):
Fixed in 2018.4.16f1