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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
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.