-
Notifications
You must be signed in to change notification settings - Fork 29.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Slow stepping through large file #86850
Comments
@weswigham here is a version of the DA that has breakpointLocations disabled, if you want to verify that this fixes it |
Errr, it actually doesn't: Check out line 1529: there's still a 3s delay between |
Yeah - definitely a v8 thing - if I revert to |
Done. It's a regression in |
I filed nodejs/node#30926, also FYI @connor4312 |
May be related to microsoft/vscode-js-debug#138 as well (I tested on 12 and marked as CNR, could have been caused by testing on >13.2) |
I don't think so. There aren't many variables being sent around. |
Looks like this will be fixed by a new version of v8 (version 8.0 or above) in node 14+. I've checked with a canary build, specifically https://nodejs.org/download/v8-canary/v14.0.0-v8-canary2020011995087de57b/ |
Great to hear! |
@weswigham pointed this out.
Every time I step while debugging in vscode, the debug adapter gets a breakpointLocations request. We should only make this request when we need to, because it could be expensive. While debugging tests in the TS codebase, there is a case where sometimes the DA's request to the runtime takes a few seconds to complete when it is triggered at the same time as a step. The result is that each step takes about 3s, which is not a good experience. The file we are debugging is 11MB which probably accounts for part of the slowness.
The text was updated successfully, but these errors were encountered: