Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2021.2.X
Votes
1
Found in
2021.2
2021.2.7f1
Issue ID
1389416
Regression
No
[2D][Tilemap] Handle has already been released error.
[2D][Tilemap] Handle has already been released error.
When playing the game, following error spawns occationally:
The Handle has already been released.
UnityEngine.StackTraceUtility:ExtractStackTrace ()
Unity.Collections.LowLevel.Unsafe.AtomicSafetyHandle:Release (Unity.Collections.LowLevel.Unsafe.AtomicSafetyHandle)
UnityEngine.Tilemaps.ITilemap:Finalize ()
Repro steps:
- Load GameContext scene
- Play the game
- Wait for the game to load to the main menu
- Start a new game.
- Above error message spawns during initial new game loading sequence.
Expected result: Tilemap handle error message does not appear during playmode
Expected result: Tilemap handle error message appears during playmode
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2022.1):
Fix for this issue available on Unity 2022.1.2f1 and above