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
- Crash on ResizeScriptingList<ScriptingObjectPtr> when passing an undeclared variable to the results parameter for GameObject.FindGameObjectsWithTag
- [Android] "Screen.safeArea.y" always returns values outside of the Safe Area when the device is in Portrait orientation
- Frame spike due to many TreeRenderer.TreeUpdated calls when repositioning terrains in large Scenes
- Crash on GameObject::RemoveComponentFromGameObjectInternal when reparenting Text GameObjects
- [IL2CPP-GarbageCollector] Changing GCMode might permanently disable GC in a multithreaded context
Add comment