Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
0
Found in
2017.4
2019.3.0f6
2020.2
Issue ID
1220442
Regression
No
Unity crash on Tilemap::SetEditorPreviewTileAsset when painting a scene by using a corrupted Tilemap
Reproduction steps:
1. Open the "SampleScene" Scene in the attached "1220442.zip" project
2. Open Tile Palette and select a 3x3 size area to paint on the Scene
3. Switch the Active Tilemap to CastleArea
4. Paint the "SampleScene" with the selected area of the Tilemap
Reproduces on:2017.4.38f1, 2018.4.18f1, 2019.3.4f1, 2020.1.0a26, 2020.2.0a2
Notes:
-The issue reproduces on 2017.4.38f1 with a Fatal Error ("GetManagerFromContext: pointer to object of manager 'RenderSettings' is NULL"), however, this error happens immediately after changing the Active Tilemap to CastleArea
First few lines of stack trace:
0x00007FF74E05AD12 (Unity) Tilemap::SetEditorPreviewTileAsset
0x00007FF74E099333 (Unity) Tilemap_CUSTOM_SetEditorPreviewTileAsset_Injected
0x00000233FF60136C (Mono JIT Code) (wrapper managed-to-native) UnityEngine.Tilemaps.Tilemap:SetEditorPreviewTileAsset_Injected (UnityEngine.Tilemaps.Tilemap,UnityEngine.Vector3Int&,UnityEngine.Object)
0x00000233FF601293 (Mono JIT Code) UnityEngine.Tilemaps.Tilemap:SetEditorPreviewTileAsset (UnityEngine.Vector3Int,UnityEngine.Object)
0x00000233FF601213 (Mono JIT Code) UnityEngine.Tilemaps.Tilemap:SetEditorPreviewTile (UnityEngine.Vector3Int,UnityEngine.Tilemaps.TileBase)
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] Crash on DetermineFileNameForNewPrefab when creating Prefab Variant
- Memory Profiler styling breaks when the SummaryView.uxml file is opened in UI Builder
- A "projectChanged" event is not triggered when Sprites are added to a SpriteAtlas
- A Memory leak occurs when the "JsonSerialization.FromJson" function is executed
- “ArgumentException: SetData()“ error when making a character with PSDImporter under specific conditions
Resolution Note (fix version 2020.2):
fixed in: 2020.2.0a5, backported to: 2020.1.0b4
Resolution Note (fix version 2019.4):
A fix for this issue is available on Unity 2019.4.30f1 and above