Search Issue Tracker
Fixed
Fixed in 2021.3.33f1, 2022.3.11f1, 2023.1.14f1, 2023.2.1f1, 2023.3.0a16, 7000.0.0a1
Votes
0
Found in
2022.3.6f1
2023.1.6f1
2023.2.0b2
Issue ID
UUM-43492
Regression
No
Crash on RaiseException when hovering over code post-breakpoint trigger in Debug Mode
Reproduction steps:
1. Open the attached “repro-project“
2. Open the “Assets/Scenes/NeonTest.unity“ scene
3. Switch the Editor to Debug Mode by clicking the bug icon, located in the lower-right corner of the Unity interface
4. Open the “Assets/Code/ECS/Systems/Nations/UnitTrainingSystem.cs“ script in Rider IDE
5. Add a breakpoint at line 69
6. In Rider IDE select the "Debug" option which is located in the upper-right corner of the Rider interface
7. Back in Unity, enter Play Mode and choose a country from the presented list
8. In the Game View window, select the army base icon (the second icon from the top) located on the left side
9. Deploy the "Infantry" unit on a green tile on the map
10. Wait for the debug point at line 69 to trigger
11. Within Rider IDE, hover over “orders.length“ at line 64 or 66
12. Observe the crash
Reproducible with: 2022.3.6f1, 2023.1.6f1, 2023.2.0b2
Could not test with: 2021.3.29f1 (could not switch to Debug Mode due to multiple errors when downgrading the project)
Reproduced on: Windows 10 Pro
First few lines of the stack traces:
0x00007FFCF3F1CF19 (KERNELBASE) RaiseException
0x00007FFC11C2064C (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\utils\mono-log-common.c:143] mono_log_write_logfile
0x00007FFC11C0C4A2 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\eglib\goutput.c:172] monoeg_g_logv_nofree
0x00007FFC11C0C57C (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\eglib\goutput.c:215] monoeg_assertion_message
0x00007FFC11C0C5E6 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\eglib\goutput.c:239] mono_assertion_message_unreachable
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment