Search Issue Tracker
Won't Fix
Votes
4
Found in
5.6.2f1
Issue ID
981714
Regression
No
Visual Studio Code "hangs" on debugging
Reproduction steps:
1. Open "MinimalRepro.zip" project
2. Open "scene1" scene
3. Open "MettaurAI" script with Visual Studio Code
4. Put a Breakpoint on line 23
5. Start Debugging
6. Enter Play mode in Unity
7. Try to "Step Into"/"Step Over"/"Step Out"/"Continue"/"Pause"
Expected Result: VSC does the corresponding action to the button
Actual Result: The buttons don't do anything/ the Debugging process seems to be frozen
Reproduced with: 2018.2.0a1, 2018.1.0b6, 2017.3.1p1, 2017.2.1p3, 2017.1.3p1, 5.6.5p1
Note:
"hangs" as in you can't proceed with stepping into or out of statements and continue/pause doesn't affect the flow of the debugging
VSC Version 1.19.3
Comments (4)
-
Sam-Sproutel
Aug 22, 2018 18:35
Seeing this most of the time
Unity 2018.2.1f1
VSCode 1.26.0
OSX 10.13.6 -
wgamestom
May 06, 2018 22:37
Same here, but not always.
Unity 2017.1.1f1
VSCode 1.23.0
OSX 10.13.5 Beta -
albertreed
Mar 04, 2018 17:41
Seeing this in 2017.3.1f1 / 1.20.1 as well.
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.