Search Issue Tracker
Won't Fix
Won't Fix in 2022.1.X
Votes
0
Found in
2021.3.16f1
2022.1.24f1
Issue ID
UUM-25091
Regression
No
InvalidFrameStackException is thrown when debugging the Update() method
Reproduction steps:
1. Open the attached project “ExceptionOnDebug“
2. Open the scene “Assets/MainScene”
3. Enter the Play Mode
4. Open the script “Assets/Plugins/External/LunarConsole/Scripts/LunarConsole.cs“ using the Visual Studio Code editor
5. Add Breakpoint to the 228th line
6. Attach Unity Debugger View>Command Pallete>Unity Attach Debugger
7. Press F11 a couple of times
8. Observe InvalidFrameStackException in the VS Code Debug Window
Expected result: Debugging process works without failure
Actual result: InvalidStackFremException is thrown randomly
Reproducible with: 2021.3.16f1, 2022.1.24f1
Couldn't test with: 2020.3.43f1 (“The type or namespace name 'PrefabStageUtility' does not exist in the namespace 'UnityEditor.SceneManagement'“), 2022.2f1 (“The type or namespace name 'NavMeshSurface' could not be found“), 2023.1.0a25 (Project crashes on launch)
Reproducible on: Windows 11
Note: The issue has been seen in VS Code and Rider editors
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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note:
Issue only happen in VS Code, and public ticket has been closed by the customer.
Resolution Note (2022.1.X):
Issue only happen in VS Code, and public ticket has been closed by the customer.