VS Code Debugger Extremely Slow to Reach First Breakpoint

Question

I'm using VS Code on Windows 10, to debug both Python and React. The debugger is extremely slow to reach the first breakpoint, for both Python and JS/Chrome. The sequence of actions I'm observing is:

VS Code's program tab lights up immediately

The first breakpoint only gets reached/highlighed 10-60 seconds later. In between it hangs. I try to click anywhere on the screen but the application is frozen.

Extensions installed:

About:

Try to enable in your launch.json: "logging": { "engineLogging": true } — kogonidze, May 19 '21 at 19:45
A bunch of messages should appear in `Debug console`. Is there anything among these entries to explain the delay? — kogonidze, May 19 '21 at 19:57
I have the same issue with debugging Angular Code in Chrome. VS Code takes some time to hit any breakpoint. Did you find any solution for it? — mor222, May 24 '21 at 11:47
No. Still waiting for any leads. I might have to re-install VS and see what happens. — gene b., May 24 '21 at 13:29
@mor222 try grabbing & moving the title bar, as I posted below. — gene b., May 26 '21 at 17:08

score 17 · Answer 1 · answered Jun 09 '21 at 20:18

17

This is a VS Code bug (one that I just spent hours diagnosing until I stumbled upon the workaround lol).

See: https://github.com/microsoft/vscode/issues/123257?_pjax=%23js-repo-pjax-container

Current workaround until May fix apparently:

Need to set the following in settings.json in VS Code

debug.focusWindowOnBreak: false

https://i.stack.imgur.com/Y223f.png

answered Jun 09 '21 at 20:18

Scott Taylor

171
2

2

This isn't an ideal solution because my VS application icon doesn't light up. But if I go back to VS I see that the breakpoint is yellow and ready. In the alternative approach (grab/move title bar), the VS application icon does light up, I just need to move the VS window to see the breakpoint. Seems like this issue was temporarily fixed in June/July, and now it came back in the latest VS release. – gene b. Aug 11 '21 at 17:00
This is a perfect solution for me because I absolutely hate that windows doesn't allow me to disable screen jacking - this is a perfect 2 birds 1 stone fix for me – Sam Nov 14 '21 at 04:12

score 11 · Answer 2 · answered May 26 '21 at 17:03

11

It looks like I found something that speeds it up. If I grab and move the title bar of VS Studio, the breakpoint gets reached and highlighted.

This is a preliminary finding, I'll edit it if I find something else.

answered May 26 '21 at 17:03

gene b.

10,512
21
115
227

1

Works for me but so weird, VSC can lag up to 30 seconds but F12 is right away! – Jeb50 Sep 11 '21 at 22:54
1

Works for me. That is really strange. VSC v1.62.1 – Daniel Szabo Nov 11 '21 at 02:13
Its worked for me also! I've to move the window – Caique Andrade Dec 01 '21 at 19:22

JerryG · Answer 3 · 2022-05-25T01:36:13.770

Here is how I solved similar issue, just for your reference.

Issue: When I try to debug node.js + angular application, the debugger takes very long time when starts node.js server before it reaches to the 1st breakpoint.
Reason: VS code scans all the JS files for a source map to typescript files.
Solution: In the launch.json configure "outFiles" to point to the JS files that you want to debug as .ts only.

Example:

{
    "type": "node",
    "request": "launch",
    "name": "Node",
    "program": "${workspaceRoot}/server/server.js",
    "cwd": "${workspaceRoot}",
    "runtimeArgs": ["--inspect-brk"],
    "runtimeExecutable": "node",
    "outFiles": [
        "${workspaceFolder}/server/lib/dist/*.js"
    ],
    "skipFiles": [
        "**/node_modules/**"
    ]
},

score 0 · Answer 4 · answered Aug 18 '23 at 07:33

0

I collapsed the "watch" panel (on the left side of a window) and removed all the variables. After this a speed (in debug mode) has been increased much!

answered Aug 18 '23 at 07:33

Andrew Androsow

11
2

VS Code Debugger Extremely Slow to Reach First Breakpoint

4 Answers4

Linked