Once start debugging failed, it cannot start again

[coderdreamworld]

Issue Type: Bug

Sometimes i write some wrong code, when start debugging it shows "Process exiting with code: 1". After that, i cant start debugging again, it always says "there is already a debug configuration running". Even if i click stop, it does not really stop.

VS Code version: Code 1.25.1 (1dfc5e5, 2018-07-11T15:43:53.668Z)
OS version: Windows_NT x64 6.1.7601

System Info

Item	Value
CPUs	Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz (4 x 3192)
GPU Status	2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on native_gpu_memory_buffers: disabled_software rasterization: disabled_software video_decode: enabled video_encode: enabled vpx_decode: unavailable_software webgl: enabled webgl2: enabled
Memory (System)	7.96GB (3.42GB free)
Process Argv	C:\Program Files\Microsoft VS Code\Code.exe
Screen Reader	no
VM	0%

Extensions (2)

Extension	Author (truncated)	Version
vscode-language-pack-zh-hans	MS-	1.25.3
Go	ms-	0.6.85

(1 theme extensions excluded)

[vscodebot]

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

• UX: allow selecting debug configuration (from status bar or command palette) without automatically starting debug (#47383)

[weinand]

I've seen this too.

[bwilcutt]

Also experiencing issue.

[isidorn]

@coderdreamworld @weinand @bwilcutt can you please give me some precise reproducable steps so I start investigating what is the issue here.

Since this is already present in stable there is no need to fix this for the recovery, so August milestone is good.

[spiskula]

Edited:
I seem to be hitting the same error, when trying to debug GO language. Dont have much experience with VS Code so I followed https://rominirani.com/setup-go-development-environment-with-visual-studio-code-7ea5d643a51a.

Just as the OP says, it looks like that if there are no errors in code debugging works. But after firs typo in code the VS/debugger seems to enter a state where even if code is fixed this keeps showing then try t o run:

'There is already a debug configuration "Launch" running.'

[isidorn]

There was a large refactoring in debug how we handle sessions.
I tried reproducing the issue described with the following code sample and I could not

process.exit(1);
console.log('hello there');

@coderdreamworld @weinand @bwilcutt So please try the latest insiders and let me know if you still see the original issue so I can reopen this. Thanks a lot

[isidorn]

Also might be a duplicate of #57255

[juristr]

@isidorn I'm experiencing this issue when attaching to node process running in debug inside a container. If the "attaching" fails (i.e. due to a timeout), and I try to relaunch it, it gives me the error that a debug session is already running. but I cannot see any and I cannot event terminate it somehow.

here's my config

{
      "type": "node",
      "request": "attach",
      "name": "Docker: Attach to Node",
      "port": 9229,
      "address": "localhost",
      "localRoot": "${workspaceFolder}/node/proxy-coordinator",
      "remoteRoot": "/home/node/app",
      "protocol": "inspector"
    },

doing a vscode reload fixes it ofc.. (using the last VSCode Insiders version)

[isidorn]

@juristr thanks a lot, I was not bobbling up the error properly, this should be fixed in latest out of source and you can verify in tomorrow's vscode insiders - thanks a lot!

[juristr]

@isidorn You guys rock 😄, didn't expect such a fast response

[isidorn]

Thanks, if the issue is good we tend to fix fast. Just let me know once you get the update if it is good for you so I can verify it.

[isidorn]

@juristr just a friednly reminder if you can verify this is good now, thanks a lot

[alexr00]

@isidorn For verification: Is there a good way to force the state that causes this to happen so I can make sure it doesn't happen?

[juristr]

@isidorn Just wanted to check whether the bug is fixed, but I'm getting a strange error now when running the exact same launch.json configuration I posted above 🤔

[isidorn]

@juristr that sounds like an unrelated issue which has something to do with source maps. Can you please create a new issue in this repository with reproducable steps fyi @roblourens
@alexr00 no need to verify this one, since Sandeep verified the issue which this is a duplicate off #59331
Removing bug label, sorry for not doing that earlier