Search Issue Tracker
Duplicate
Votes
0
Found in
2017.4.0f1
2018.4.0f1
2019.1.0a1
2019.1.4f1
2019.2.0a1
2019.3.0a1
Issue ID
1168179
Regression
No
[VSCode]During debugging Unity Editor receives StackOverflow/ThreadAbortException errors, exiting debug results in Editor freeze
How to reproduce:
1. Open attached project "DebugRepro.zip" and scene "TestDebugger"
2. Make sure that Edit -> Preferences -> External Tools -> External Script Editor is set to Visual Studio Code
3. In Project window, open up "DebugScript" script
4. In Visual Studio Code, put breakpoint on line 12 and start Debugging (hotkey F5)
5. In Unity, enter Play mode
6. In Visual Studio Code, hover over "List" variable, expand "[0..99]" after that expand "[0]"
7. In Visual Studio Code, stop Debug mode
8. In Unity, exit Play mode
9. Observe Unity Editor
Expected result: no errors are thrown, the editor works as expected
Actual result: "StackOverflowException: The requested operation caused a stack overflow." and "ThreadAbortException" are thrown, Unity freezes
Reproducible with: 2017.4.30f1, 2018.4.4f1, 2019.1.10f1, 2019.2.0b9, 2019.3.0a9
-
Resolution Note:
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
This is a duplicate of issue #1130912