Search Issue Tracker
Duplicate
Votes
0
Found in
2017.3.0a2
Issue ID
938064
Regression
No
[New Scripting Runtime] Visual Studio Code doesn't break at breakpoints and freezes Editor
1. What happened
[New Scripting Runtime] While debugging, Visual Studio Code doesn't break at breakpoints and freezes the Editor after the debugger is detached.
The same scenario works fine for the legacy runtime.
2. How we can reproduce it using the example you attached
- Open scene 1
- Open TestScript.cs with VSCode
- Put breakpoint on line 9 : Debug.Log("asdf");
- Start debugger for Unity Editor config (I'm using this ext: https://marketplace.visualstudio.com/items?itemName=Unity.unity-debug)
- Switch to Editor and Play
>>> Notice that Console reports 'asdf' but the breakpoint wasn't hit.
- Exit Play mode
- Stop debugger
- Return to Editor and wait for a few seconds (usually about 5-10 seconds).
>>> Editor stops responding
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment