vscode: VSCode restart debugging not working anymore

I’m using VSCode debugging to debug Node.js application. Whenever I try to restart the debugging after making changes in the code it terminates the debugging.

I get this error in the logs:

[2019-12-27 16:23:07.775] [renderer1] [error] timeout after 500 ms: Error: timeout after 500 ms
    at t.RawDebugSession.handleErrorResponse (file:///C:/Users/neosoft_sushantk/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:2821:819)
    at file:///C:/Users/neosoft_sushantk/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:2821:250
    at async t.RawDebugSession.shutdown (file:///C:/Users/neosoft_sushantk/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:2819:336)
    at async R.terminate (file:///C:/Users/neosoft_sushantk/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:5113:637)
    at async Y.restartSession (file:///C:/Users/neosoft_sushantk/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:5138:397)

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 4
Comments: 42 (11 by maintainers)

Most upvoted comments

I am having the same problem since 2-3 weeks ago. Restart button just end the debug session. But thanks to this comment, double click solve the problem. Double click on restart button restart debug session. It used to be single click tho.

PyaePhyoKhant on Jan 16, 2020

Restart ends the debug session

SushKenyNeosoft on Jan 14, 2020

@PyaePhyoKhant double click worked for me too 😃. Thanks sir! @weinand but it’s weird though

SushKenyNeosoft on Jan 16, 2020

@SushKenyNeosoft It is strange.

It is working for me properly on Win 10. But it is not on Ubuntu 18.04.

I also tried debug with multiple languages (python, js and go) and found out that only python is having problem which is my main language. Other language debuggers js and go are working properly. It seem to me that only our commonly used language is having problem.

I tried rolling back vscode version but still had same problem.

Same here the only difference is I’m using Node.js

SushKenyNeosoft on Jan 30, 2020

@weinand I am using version 1.14.1 and node.js 12.4.0 and I am using windows 10, I haven’t done any recent updates that caused it to break, only security fixes.

Debugger is the one build in for node.js

"version": "0.2.0",
"configurations": [
    {
        "type": "node",
        "request": "launch",
        "name": "Launch Program",
        "skipFiles": [
            "<node_internals>/**"
        ],
        "program": "${workspaceFolder}\\index.js"
    }
]

TijsDeBelie on Jan 29, 2020

@weinand It’s working properly in Windows 7 and Ubuntu, the problem is in Windows 10.

SushKenyNeosoft on Jan 29, 2020

Have you considered to use “nodemon”? With nodemon your app is restarted automatically when a source change is detected and VS Code will start the debug session automatically as well. So “zero clicks” instead of one or two…

weinand on Jan 6, 2020

This has been mentioned in https://github.com/microsoft/vscode/issues/85386 and https://github.com/microsoft/vscode/issues/86800

I get the same error. Disabling all extensions makes the problem go away, and if I only enable Python extension (since my project is in Python), and try to run it there, I get the same error message.

elahmo on Jan 1, 2020