Menu
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:
Extensions installed:
About:
940
If a source file has changed and the source no longer matches the code you're debugging, the debugger won't set breakpoints in the code by default. Normally, this problem happens when a source file is changed, but the source code wasn't rebuilt. To fix this issue, rebuild the project.
One of the key features of Visual Studio Code is its great debugging support. VS Code's built-in debugger helps accelerate your edit, compile, and debug loop.
If a breakpoint is reached, or a signal not related to stepping occurs before count steps, stepping stops right away. Continue to the next source line in the current (innermost) stack frame. This is similar to step , but function calls that appear within the line of code are executed without stopping.
Run to a breakpoint in code To set a simple breakpoint in your code, select the far-left margin next to the line of code where you want to suspend execution. You can also select the line and then select F9, select Debug > Toggle Breakpoint, or right-click and select Breakpoint > Insert Breakpoint.
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
161
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.
11
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
