When hitting Stop during Debug, it does not always kill debug process

[intdel]

I am running a web server in Go (1.6) with visual studio code and the most recent plugin:

func main() {

    http.HandleFunc("/data", htmlHandler)

    err := http.ListenAndServe(":8080", nil)
    if err != nil {
        log.Fatal(err)
    }
    os.Exit(0)
}

When I hit the stop button on the small debug window, it does not kill the webserver, because after I hit F5 again I get:

2016/08/16 15:34:13 server.go:71: Using API v1
2016/08/16 15:34:13 debugger.go:61: launching process with args: [./debug]
API server listening at: 127.0.0.1:2345
2016/08/16 15:34:13 debugger.go:393: continuing
2016/08/16 15:34:13 listen tcp :8080: bind: address already in use

So I will have to look manually for the PID and kill it. Then it works again.

[lukehoban]

What OS, and do you have a full precise repro? I tried a few times on Windows and OSX with the closest full example I could derive from the above and couldn't reproduce this.

Happy to reopen if you have more info to investigate.

[intdel]

Sure. I am using Debian Testing with Google Chrome Version 52.0.2743.116 (64-bit) and VS code Version 1.4.0:

lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux testing (stretch)
Release:    testing
Codename:   stretch

Here is an example code that I used to successfully verify the issue:
web.go:

package main

import "net/http"
import "fmt"
import "log"

func welcomeHandler(w http.ResponseWriter, r *http.Request) {

    fmt.Fprintln(w, "hello")
}

func main() {

    http.HandleFunc("/", welcomeHandler)

    err := http.ListenAndServe(":8080", nil)

    if err != nil {
        log.Fatal(err)
    }

}

launch.json:

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Launch",
            "type": "go",
            "request": "launch",
            "mode": "debug",
            "remotePath": "",
            "port": 2345,
            "host": "127.0.0.1",
            "program": "${workspaceRoot}",
            "env": {},
            "args": [],
            "showLog": true
        }
    ]
}

Steps to reproduce:

1. Press F5 to launch the debug process
2. Open terminal and do pidof debug:

$ pidof debug                                                                                                                                                       
5441     

\3. Open browser and go to http://localhost:8080. You will see "hello
4. Hit the red stop button in VS Code
5. Refresh browser again and it's still hello
6. Pidof again:

$ pidof debug                                                                                                                                                       
5441    

\7. Hit F5 again and you will get error
:

2016/08/21 19:13:05 server.go:71: Using API v1
2016/08/21 19:13:05 debugger.go:61: launching process with args: [./debug]
API server listening at: 127.0.0.1:2345
2016/08/21 19:13:06 debugger.go:393: continuing
2016/08/21 19:13:06 listen tcp :8080: bind: address already in use

You can use pidof again and you will see that it is still the same process.

[jaylittle]

Can confirm this. Seeing this exact same behavior with go debugging using this vscode extension on Arch Linux.

[bsphere]

same behavior with Ubuntu 16.04 and vscode 1.5.1

[therox]

• vscode 1.5.2, Ubuntu 16.04

[d10r]

Same here. Ubuntu 14.04, vscode 1.6.0, vscode-go 0.6.44

[roblourens]

I can repro this, and confirm that it works correctly with delve. So maybe we can do whatever delve does.

[Polarbear2121]

Hi,

I'm getting the same messages

2016/10/22 13:37:09 server.go:71: Using API v1
2016/10/22 13:37:09 debugger.go:61: launching process with args: [./debug]
API server listening at: 127.0.0.1:2345
2016/10/22 13:37:09 debugger.go:393: continuing

Is there a way to clear the messages?

Thank you

OSX 10.12
GO 1.7.3
GO Plug-in 0.6.45

[intdel]

@jferrer21 As far as I can see, your messages are not "errors" but rather informative. It would be an error if it had the line 2016/08/21 19:13:06 listen tcp :8080: bind: address already in use. Maybe you omitted it when pasting it?

Otherwise you can get rid of those messages by setting "showLog": true to "showLog": false in launch.json

[Polarbear2121]

I didn’t get the last line. Thank you for the info, about setting the showLog.

[nezorflame]

Getting the same behaviour on Mint 18 with the vscode 1.7.1 and go 1.7.3.
"debug" process is not being killed after Stop button is pressed.