Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4
2019.4
2020.2
2021.1
2021.1.0b4
2021.2
Issue ID
1310990
Regression
No
Editor freezes when IDE debugger hits a breapoint in a method with MenuItem attribute
WARNING:
Make sure the Task Manager is closed before reproducing this issue! You will not be able to open any applications that are already open on Windows 10 taskbar, however, you can still use the Ctrl+Shift+Esc shortcut to open the Task Manager and kill the IDE process.
Reproduction steps:
1. Open the user's attached "ValidatorFunctionFreeze.zip" project
2. Open the MenuItem.cs script
3. Set a breakpoint at line 17 (in ExecuteValidation method)
4. Attach a debugger and return to Unity Editor
5. Click on the "Example" in the menu bar
-- Observe the Editor freeze
Reproducible with: 2018.4.32f1, 2019.4.20f1, 2020.2.5f1, 2021.1.0b7, 2021.2.0a4
Tested with:
- Visual Studio Code
- Visual Studio 2019
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
- 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
Resolution Note:
This is a limitation of the Mono debugger on Windows.
Current workaround is to run Unity and Visual Studio side by side when debugging such code (instead of running Unity in full screen)