Search Issue Tracker
Not Reproducible
Votes
0
Found in
2017.4.0f1
2018.3.0b4
2019.1.0a1
2019.2.0a1
2019.2.0f1
2019.3.0a1
Issue ID
1174254
Regression
No
Crash on Tilemap::RefreshTileAsset when opening a Scene with a specific Tilemap
1. Open the user's attached project 'pixel-golf.zip' project
2. Open 'Menu' Scene
-- observe the crash
Reproducible in: 2017.4.31f1, 2018.4.6f1, 2019.1.141, 2019.2.1f1, 2019.3.0a12
First five stack trace lines (Linux):
#0 0x0055aeedcb7b47 in Tilemap::RefreshTileAsset(math::int3_storage const&, TilemapRefCountedData<PPtr<Object> > const&, bool)
#1 0x0055aeedcbc5ac in Tilemap::ValidateAllTileAssets()
#2 0x0055aeedcbd2b4 in Tilemap::Update()
#3 0x0055aeecbe1642 in void BaseBehaviourManager::CommonUpdate<BehaviourManager>()
#4 0x0055aeecbe13c8 in BehaviourManager::Update()
Notes:
The crash can be subverted by removing all Tilemap / Tilemap Renderer objects. You can do that by opening the Scene in a Code or Text editor.
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
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
- [Linux] Touch freezes in Player when any mouse button is clicked
- UnityEngine.Rendering.Volume.OnEnable() is called twice before OnDisable() creating multiple copies of the same volume when a volume is enabled right after Domain Reload when entering Play Mode
- Hinge Joint transforms are reset when toggling the "useMotor" property
- Motion Vector texture reports incorrect Mesh data when Mesh is coming from off-screen
Resolution Note:
The scene files in the project seem to have an invalid YAML format, so when loading the Tilemap from the scene file, it loaded corrupt data which resulted in the crash. Fixing the invalid YAML format will make the scene file work again.
We are unable to reproduce the corruption of the scene file while upgrading from Unity 2017 to Unity 2019. If that occurs again, please do let us know.