Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
2018.1.0a2
2018.2.0a1
Issue ID
999177
Regression
Yes
Visual Studio Code can't start debug, because "Multiple targets ... running"
Reproduction steps:
1. Create a New Project
2. Create a Script and open it with Visual Studio Code
3. Try to debug
Expected Result: The Debugging process starts
Actual Result: Error appears, "Multiple targets with name 'Unity Editor' running. Unable to connect."
Fixed in: Visual Studio Code Debugger extension v1.3.0
Reproduced with: 2018.2.0a1, 2018.1.0b6, 2018.1.0b1, 2018.1.0a7, 2018.1.0a6, 2018.1.0a4, 2018.1.0a3(a20833), 2018.1.0a3(f88474), 2018.1.0a2
Did not reproduce on: 2018.1.0a1, 2017.3.1p1, 2017.2.1p4
Note:
VSC Version 1.19.3
Workaround:
Start "Task Manager" -> Open up the "Unity" process list -> Click on "UnityCrashHandler64" -> "End task"
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment