Search Issue Tracker
Fixed in 2019.2
Fixed in 2018.4, 2019.1
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
- [Linux] Unity licensing command on Linux pops a progress bar when using -batchmode and -nographics
- SerializedReference GameObject property gets set to null after entering Play mode
- Profiler - RawFrameDataIterator ThreadID will always return 0 for profiler frame data loaded from .data files
- Crash on scripting_field_get_type when a Script has List<> of LayoutKind.Explicit struct with [FieldOffset(1)] ScriptableObject
- Frame Debugger doesn't work when using Camera.SetTargetBuffers
Resolution Note (fix version 2018.4):
Fixed in 2018.4.16f1