Useful or not, from you.
vscode Starting inspector on 127.0.0.1:9229 failed: address already in use with nodemon

I am getting the same issues as this issue: https://github.com/Microsoft/vscode/issues/27794

Version: 1.32.3 Commit: a3db5be9b5c6ba46bb7555ec5d60178ecc2eaae4 Date: 2019-03-14T23:38:49.842Z Electron: 3.1.6 Chrome: 66.0.3359.181 Node.js: 10.2.0 V8: 6.6.346.32 OS: Linux x64 4.10.0-32-generic Steps to Reproduce:

Hitting me (changed)
[nodemon] files triggering change check: application/index.ts
[nodemon] matched rule: /home/karl/dev/a-vdgs-server/application/**/*
[nodemon] changes after filters (before/after): 1/1
[nodemon] restarting due to changes...
[nodemon] application/index.ts

[nodemon] starting `node -r ts-node/register --inspect=9229 ./application/server.ts`
[nodemon] spawning
[nodemon] child pid: 22626
Debugger listening on ws://127.0.0.1:9229/d3273c04-8fe5-4130-b02c-a6ee36bc6979
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
NODE_ENV is set to: development
Loaded config/development.json configuration file
Config lib initialized
Adding console log transport
2019-05-16T12:20:58.539Z info: Log lib initilized1
2019-05-16T12:20:58.555Z info: Websocket server started on port: 8081
2019-05-16T12:20:58.556Z debug: Connecting to MQTT broker on: mqtt://172.17.0.2
2019-05-16T12:20:58.595Z info: MQTT lib initilized
2019-05-16T12:20:58.606Z info: HTTP server running on: http://localhost:8080
2019-05-16T12:20:58.624Z debug: Connected to MQTT broker on: mqtt://172.17.0.2
2019-05-16T12:20:58.636Z debug: Presence!
2019-05-16T12:20:58.644Z debug: Hello mqtt
[nodemon] files triggering change check: application/index.ts
[nodemon] matched rule: /home/karl/dev/a-vdgs-server/application/**/*
[nodemon] changes after filters (before/after): 1/1
[nodemon] restarting due to changes...
[nodemon] application/index.ts

[nodemon] starting `node -r ts-node/register --inspect=9229 ./application/server.ts`
[nodemon] spawning
[nodemon] child pid: 22713
Debugger listening on ws://127.0.0.1:9229/785cd083-92e5-4c01-afd0-c945c2bcfa02
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
NODE_ENV is set to: development
Loaded config/development.json configuration file
Config lib initialized
Adding console log transport
2019-05-16T12:21:06.992Z info: Log lib initilized1
2019-05-16T12:21:07.004Z info: Websocket server started on port: 8081
2019-05-16T12:21:07.005Z debug: Connecting to MQTT broker on: mqtt://172.17.0.2
2019-05-16T12:21:07.038Z info: MQTT lib initilized
2019-05-16T12:21:07.043Z info: HTTP server running on: http://localhost:8080
2019-05-16T12:21:07.052Z debug: Connected to MQTT broker on: mqtt://172.17.0.2
2019-05-16T12:21:07.055Z debug: Presence!
2019-05-16T12:21:07.057Z debug: Hello mqtt
[nodemon] files triggering change check: application/index.ts
[nodemon] matched rule: /home/karl/dev/a-vdgs-server/application/**/*
[nodemon] changes after filters (before/after): 1/1
[nodemon] restarting due to changes...
[nodemon] application/index.ts

[nodemon] starting `node -r ts-node/register --inspect=9229 ./application/server.ts`
[nodemon] spawning
[nodemon] child pid: 22789
Starting inspector on 127.0.0.1:9229 failed: address already in use
[nodemon] app crashed - waiting for file changes before starting...

launch.json

        {
            "type": "node",
            "request": "launch",
            "name": "dev",
            "runtimeExecutable": "nodemon",
            "runtimeArgs": ["--config", "./nodemon.debug.json"],
            "cwd": "${workspaceRoot}",
            "restart": true,
            "port": 9229,
            "env": {
                "NODE_ENV": "development"
            },
            "outputCapture": "std",
            "console": "integratedTerminal"
        },

nodemon.json

{
    "watch": ["application"],
    "ext": "ts",
    "ignore": ["./**/*.spec.ts"],
    "exec": "node -r ts-node/register --inspect=9229 ./application/server.ts",
    "verbose": true
}

The behavior I see is that it randomly happens. My best guess is that the previous attached debugger hasn't finished closing down when the new one tries to start up on the same port. This is due to the "restart": true. I don't know how this process works but from what I read it keeps track of the node process, but does it keep track of the previous debugger?

That's a useful answer
Without any help

on my mac, debugger is not working

debugging protractor (angular8)

visual studio code version:

Version: 1.45.1
Commit: 5763d909d5f12fe19f215cbfdd29a91c0fa9208a
Date: 2020-05-14T08:33:47.663Z
Electron: 7.2.4
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 19.3.0

Error on debugger console

/usr/local/bin/node --inspect-brk=16749 node_modules/protractor/bin/protractor /Users/siva/Documents/aiq-ui-e2e/protractor-aiq-stg.conf.js 
Debugger listening on ws://127.0.0.1:16749/d7d3518f-9e2f-4191-a22a-bf1f0c3f193a
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
[12:46:58] I/launcher - Running 1 instances of WebDriver
logger.js:158
[12:46:58] I/testLogger - 
------------------------------------

logger.js:158
[12:46:58] I/testLogger - [chrome #01-0] PID: 60424
[chrome #01-0] Specs: /Users/siva/Documents/aiq-ui-e2e/src/modules/aiq/renewals/testCases/TC_001.e2e-spec.ts
[chrome #01-0] 
[chrome #01-0] Starting inspector on 127.0.0.1:16749 failed: address already in use

logger.js:158
[12:46:58] I/testLogger - 

logger.js:158
[12:46:58] E/launcher - Runner process exited unexpectedly with error code: 12
logger.js:158
[12:46:58] I/launcher - 1 instance(s) of WebDriver still running
logger.js:158
[12:46:58] I/testLogger - 
------------------------------------

lsof -i:portNumber is not helping me. when i run this command, there is no process is actually running.