vscode: Debug "Step Into" Slow
Type: Performance Issue
When I step into my code (NodeJS), I noticed lately that the debugger is slower upon stepping in or over. I don’t recall having this issue before though. It’s a slight lag. I tried clearing my cache but that seemed to have no effect.
VS Code version: Code 1.79.2 (695af097c7bd098fbf017ce3ac85e09bbc5dda06, 2023-06-14T08:57:04.379Z) OS version: Windows_NT x64 10.0.19045 Modes:
System Info
| Item | Value |
|---|---|
| CPUs | AMD Ryzen 7 3800X 8-Core Processor (16 x 3880) |
| GPU Status | 2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled |
| Load (avg) | undefined |
| Memory (System) | 31.89GB (18.14GB free) |
| Process Argv | –crash-reporter-id fabd597e-7465-4a75-969f-01937aaa0b28 |
| Screen Reader | no |
| VM | 0% |
Workspace Info
| Window (launch.json - nodejs_barebones (Workspace) - Visual Studio Code [Administrator])
| Folder (nodejs_barebones): 28 files
| File types: json(5) js(4) ts(2) map(2) gitattributes(1) gitignore(1)
| code-workspace(1) html(1) md(1)
| Conf files: launch.json(1) tasks.json(1) package.json(1)
| webpack.config.js(1) tsconfig.json(1)
| Launch Configs: node(2) chrome;
Extensions (9)
| Extension | Author (truncated) | Version |
|---|---|---|
| vscode-css-formatter | aes | 1.0.2 |
| classdiagram-ts | Ale | 0.1.67 |
| jsonviewer | cci | 1.3.2 |
| javascript-ejs-support | Dig | 1.3.3 |
| gitlens | eam | 14.0.1 |
| vscode-firefox-debug | fir | 2.9.8 |
| debug-visualizer | hed | 2.4.0 |
| hexeditor | ms- | 1.9.11 |
| php-debug | xde | 1.32.1 |
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 21 (7 by maintainers)
Commits related to this issue
- debug: improve performance of stepping Previously we did not show a next-stepped state until the entire stackframe was retrieved, which led to the issue this fixes #185708. This queuing was done to p... — committed to microsoft/vscode by connor4312 8 months ago
- debug: improve performance of stepping (#197397) Previously we did not show a next-stepped state until the entire stackframe was retrieved, which led to the issue this fixes #185708. This queuing was... — committed to microsoft/vscode by connor4312 8 months ago
Just as I was accepting that this debugger would always have latency issues, I get this notification today. I immediately installed Insiders, and…coming from someone who uses this style of debugging all the time, I can confirm this has been fixed! I will continue to test of course, but so far this is the fastest I’ve ever seen the step into debugger work, even before this had been a verifiable problem.
Thanks for addressing this. As someone who debugs code 90% of the time, this was pleasant surprise to see fixed!
/verified