Search Issue Tracker
Active
Votes
0
Found in
2021.3.44f1
2022.3.50f1
6000.0.23f1
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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor crashes when debugging a for loop
- Crash on UnityPlayer!profiling::ProfilerManager::DisposeProfilerRecorder+0xa when Player gets relaunched and exited after running for a long amount of time
- [Input system] When releasing one touch and pressing a second touch during a single frame, the second touch is not translated into UI event line OnPointerDown by the InputSystemUIInputModule
- URP Samples - multiple "Attempting to resolve render surface" and other errors appear when setting Quality pipeline asset
- OnDemandRendering.willCurrentFrameRender returns incorrect values in the Player when UnityEngine.Rendering.OnDemandRendering.renderFrameInterval is greater than 1
Add comment