Error displayed when debug process isn't running: "There is already a debug configuration "launch" running."

[dgiridharan]

Steps to reporduce:

1. Create a main function with compile error:

package main

import (
	"fmt"
)

func main() {
	// compile error
	oisjdflsdfkj

	fmt.Printf("Hello World")
}

2. Create a new Configuration to launch this file:

    {
      "name": "Launch file",
      "type": "go",
      "request": "launch",
      "mode": "debug",
      "program": "path to the go main function file"
    },

3. Launch the debug configuration give you an error:
   "Failed to continue: Check the debug console for deatils."
4. Click cancel on the error dialog
5. Remove the compile error:

package main

import (
	"fmt"
)

func main() {
	// Compile error removed

	fmt.Printf("Hello World")
}

6. Save and launch the same debug configuration gives you an error:
   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.

[dgiridharan]

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!

[tianyouhui]

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%

[louspringer]

The experimental patch at #1833 fixes the issue for me.

[ramya-rao-a]

Please see #1814 (comment)

I'll be releasing an update in a day or two.

Thanks for your patience.

[ramya-rao-a]

The fix is now available in the latest update (0.6.86) to the Go extension

[dgiridharan]

Ramya Rao (@ramya-rao-a) - Thanks lot! That was really fast.