Search Issue Tracker
Fixed
Fixed in 6000.0.55f1, 6000.1.15f1, 6000.2.0b11, 6000.3.0a3
Votes
0
Found in
2022.3.63f1
6000.0.51f1
6000.1.8f1
6000.2.0b6
6000.3.0a1
Issue ID
UUM-110584
Regression
No
Freeze when entering Play Mode with a certain Tilemap enabled
How to reproduce:
1. Open the attached “CrashRepro“ project
2. Open the “Assets/Scenes/SampleScene.unity“ Scene
3. Enter Play Mode
Reproducible with: 2022.3.63f1, 6000.0.51f1, 6000.1.8f1, 6000.2.0b6, 6000.3.0a1
Reproducible on: macOS 15.5 Sequoia (Intel), Windows 10 (by user)
Not reproducible on: No other environment tested
Note: If the “Tilemap“ GameObject of the parent “Grid“ GameObject is disabled in the Hierarchy, then Unity no longer freezes in Play Mode
First few lines of the stack trace:
0x00007FFA962BA3BA (KERNELBASE) RaiseException
0x00007FFA1062AEC2 (Unity) LaunchBugReporter
0x00007FFA0FEEFABF (Unity) EditorMonoConsole::LogToConsoleImplementation
0x00007FFA0FEF05BA (Unity) EditorMonoConsole::LogToConsoleImplementation
0x00007FFA10BA36DD (Unity) DebugStringToFilePostprocessedStacktrace
0x00007FFA10BA2A78 (Unity) DebugStringToFile
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
- Multiple errors are thrown in the console while using perforce when moving an asset using shortcuts
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Asset name is not shown in the Undo History window when a sprite is modified
Resolution Note (fix version 6000.3.0a3):
Fix for this issue is available on Unity 6000.3.0a3 and above
Resolution Note (fix version 6000.2.0b11):
Fix for this issue is available on Unity 6000.2.0b11 and above
Resolution Note (fix version 6000.1.15f1):
Fix for this issue is available on Unity 6000.1.15f1 and above
Resolution Note (fix version 6000.0.55f1):
Fix for this issue is available on Unity 6000.0.55f1 and above