This repository has been archived by the owner on Jul 15, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 646
Error displayed when debug process isn't running: "There is already a debug configuration "launch" running." #1840
Comments
This is really really bad user experience. Is it possible to fix this issue soon? This happens any time I have an error for launching a debug configuration and I attempt to relaunch after fixing the issue. It would be fine if there's a work around for this as well (for the time being). Thanks again, I really appreciate it! |
Also, when I updated vscode to 1.25.1 (or even lower 1.25?), the vscode and vscode-go becomes very stutter, and cpu runs heavily ... 100% |
dgiridharan
changed the title
Error displayed when not applicable: "There is already a debug configuration "launch" running."
Error displayed when debug process isn't running: "There is already a debug configuration "launch" running."
Aug 12, 2018
The experimental patch at #1833 fixes the issue for me. |
Please see #1814 (comment) I'll be releasing an update in a day or two. Thanks for your patience. |
The fix is now available in the latest update (0.6.86) to the Go extension |
@ramya-rao-a - Thanks lot! That was really fast. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Steps to reporduce:
"Failed to continue: Check the debug console for deatils."
There is already a debug configuration "Launch file" running.
NOTE:
If I change the launch file configuration name and run the new configuration then I can run it. After it's run, there is a new entry in the call stack with an orphaned process running. I can't stop it or remove it from stopping.
The text was updated successfully, but these errors were encountered: