Search Issue Tracker
Fixed
Fixed in 2021.3.12f1, 2022.1.23f1, 2022.2.0b10, 2023.1.0a15
Votes
0
Found in
2021.3.9f1
2022.1.15f1
2022.2.0a17
2023.1.0a6
Issue ID
UUM-9219
Regression
No
Crash on method_commands_internal when Unity is attached to Visual Studio and a breakpoint is set
Reproduction steps:
1. Open the user’s attached project “UIElements.zip“
2. In the Project window open the “EventHelpers.cs” script (Packages > UI Test Framework > Runtime) with Visual Studio
3. In the Test Runner window run the “DelayTextFieldNotImmediate“ test and open its source code
4. In Visual Studio select the “EventHelpers.cs“ script and press the “Attach it to Unity” button
5. Add a breakpoint
Expected result: Unity does not crash
Actual result: Unity crashes
Reproducible with: 2022.2.0a17
Could not test with: 2020.3.36f1, 2021.3.5f1, 2022.1.8f1, 2023.1.0a2 - due to errors “EventHelpers.cs methods are inaccessible due to its protection level”
Reproduced on: Windows 10 Pro
Notes:
- Reproduces with Visual Studio 2019 and Visual Studio 2022
Stack trace:
0x00007FF8314D5DB9 (mono-2.0-bdwgc) \[C:\\build\\output\\Unity-Technologies\\mono\\mono\\mini\\debugger-agent.c:8861] method_commands_internal
0x00007FF8314DA675 (mono-2.0-bdwgc) \[C:\\build\\output\\Unity-Technologies\\mono\\mono\\mini\\debugger-agent.c:10440] debugger_thread
0x00007FF83130D6AB (mono-2.0-bdwgc) \[C:\\build\\output\\Unity-Technologies\\mono\\mono\\metadata\\threads.c:1268] start_wrapper_internal
0x00007FF83130D886 (mono-2.0-bdwgc) \[C:\\build\\output\\Unity-Technologies\\mono\\mono\\metadata\\threads.c:1344] start_wrapper
0x00007FF8DEF57034 (KERNEL32) BaseThreadInitThunk
0x00007FF8E0D42651 (ntdll) RtlUserThreadStart
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
- Prefab Override popup displays on wrong monitor when Inspector width is resized to minimum
- Scroll View is not moving by inertia after scrolling by click and dragging when Editor window is minimized and Canvas "Render Mode" is set to "World Space"
- "type mismatch error" occurs when the currentDirectionWS output of a Sample Water Surface node is connected to a float3 input
- URP Material Upgrade utility does not enable Alpha Clipping when material had Rendering Mode set to Cutout
- Particle System emission ignores the Sprite Atlas when using a Material that has the "Include in Build" setting unchecked
Resolution Note (fix version 2023.1.0a15):
Fixed in: 2023.1.0a15
Resolution Note (fix version 2022.2.0b10):
Fixed in: 2022.2.0b10
Resolution Note (fix version 2022.1.23f1):
Fixed in: 2022.1.23f1
Resolution Note (fix version 2021.3.12f1):
Fixed in: 2021.3.12f1