Search Issue Tracker
Fixed
Fixed in 2021.3.25f1, 2022.2.18f1, 2023.1.0b15, 2023.2.0a13
Votes
0
Found in
2020.3.47f1
2021.3.22f1
2022.2.15f1
2023.1.0b11
2023.2.0a10
Issue ID
UUM-32832
Regression
No
Tilemap with corrupted data crashes the Editor when calling CompressBounds
How to reproduce:
1. Open the attached project “tilemapcompressboundsbugtest.zip“
2. Open the “SampleScene” Scene
3. Select the “tilemap_wall1“ GameObject (child of “grid“ GameObject) in the Hierarchy
4. Press “compress” in the Inspector
Expected result: The Editor doesn’t crash
Actual result: The Editor crashes
Reproducible with: 2020.3.47f1, 2021.3.22f1, 2022.2.15f1, 2023.1.0b11, 2023.2.0a10
Reproduced on: macOS 13.0.1 (Intel), Windows 10 (by reporter)
Note: The corrupted tile can be found by opening the SampleScene file via text editor and searching for a tile with an “m_TileIndex: 3651547248“ Index and a “m_TileSpriteIndex: 4294967295“ Sprite Index
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note (fix version 2023.2.0a13):
Fix for this issue will be available on Unity 2023.2.0a13 and above
Resolution Note (fix version 2023.1.0b15):
Fix for this issue will be available on Unity 2023.1.0b15 and above
Resolution Note (fix version 2022.2.18f1):
Fix for this issue will be available on Unity 2022.2.18f1 and above
Resolution Note (fix version 2021.3.25f1):
Fix for this issue will be available on Unity 2021.3.25f1 and above