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
- Popup windows spawn on the incorrect monitor when the Editor is placed near the boundary of scaled monitor next to a monitor with different scaling
- Hidden Tabs do not shift into empty space after closing visible Tabs
- [Android] Application not deployed on a device when "activity-alias" is used in the AndroidManifest
- Shader compile process adds shader ID to the constant buffer name when the word "Globals" is being used in Vulkan
- Audio Mixer Snapshot link to the documentation isn’t working
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)