Search Issue Tracker
Won't Fix
Won't Fix in 6000.1.X
Votes
1
Found in
2022.3.50f1
6000.0.23f1
6000.1.0a2
Issue ID
UUM-83946
Regression
No
Editor crashes when debugging a for loop
Reproduction steps:
1. Open the attached “Repro“ project
2. Open the “TestScene.unity“
3. Open your debugger of choice and attach it to the Editor
4. Place a breakpoint on the 11th line of the “Assets/TestComponent.cs” Script
5. Enter the Play Mode
Expected result: The debugger steps into the loop
Actual result: Editor crashes
Reproducible with: 2021.3.44f1, 2022.3.50f1, 6000.0.23f1
Reproducible on: M1 Max MacOS 14.6.1
Not reproducible on: No other environment tested
Notes:
- No stack trace was produced
- The Script executes as expected without debugging
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:
Infinite recursion in a ToString() implementation caused a stack overflow, triggering the crash.
Resolution Note (6000.1.X):
Infinite recursion in a ToString() implementation caused a stack overflow, triggering the crash.