Search Issue Tracker
Third Party Issue
Votes
0
Found in
2022.1.10f1
2022.2.0a11
2023.1.0a4
Issue ID
UUM-9350
Regression
Yes
Crash on method_commands_internal when debugging a script that has an Assembly Definition Asset
Reproduction steps:
1. Open user attached project.
2. Open “Assets/Scripts/postprocessor/post_process_sprite.cs”
3. Toggle breakpoint on line 10
4. Click “Attach to Unity”
Expected result: Unity editor does not crash
Actual result: Unity editor crashes
Reproducible with: 2022.1.0a13, 2022.1.10f1, 2022.2.0a11, 2023.1.0a4
Not reproducible with: 2020.3.37f1, 2021.3.6f1, 2022.1.0a12, 2022.2.0a12, 2022.2.0b1, 2023.1.0a3
Reproducible on: Windows 10 Pro 21H2
Note: You have to reimport the project on every version tested.
Stacktrace:
{noformat}0x00007FF8FEE254BA (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\mini\debugger-agent.c:8719] method_commands_internal
0x00007FF8FEE26E8B (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\mini\debugger-agent.c:9087] method_commands
0x00007FF8FEE29F78 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\mini\debugger-agent.c:10289] debugger_thread
0x00007FF8FEC5D6AB (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\metadata\threads.c:1268] start_wrapper_internal
0x00007FF8FEC5D886 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\metadata\threads.c:1344] start_wrapper
0x00007FF9CD527034 (KERNEL32) BaseThreadInitThunk
0x00007FF9CEA02651 (ntdll) RtlUserThreadStart{noformat}
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
- 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
Resolution Note:
After investigation this was determined to be an issue with Visual Studio's debugger. Microsoft is aware of the issue and is fixing it under the following bug: https://developercommunity.visualstudio.com/t/Unity-crashes-when-setting-a-breakpoint/10102204