You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: avoid blocking or activating the BP predictor when unnecessary
Previously, we always waited on the breakpoint predictor unless it was
explicitly disabled. This was unnecessary in two cases:
- If we were able to set an instrumentation breakpoint, this was
redundant since we use that to ensure breakpoints get set before
scripts run.
- We used it even if the source in question was already loaded. This is,
while _technically_ useful if a source was present in multiple scripts
(e.g. present in multiple webpack bundles), usually not practically
necessary, as we do still set the breakpoint if/when that script is parsed.
Fixesmicrosoft/vscode#153470
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ This changelog records changes to stable releases since 1.50.2. "TBA" changes he
4
4
5
5
## Nightly (only)
6
6
7
-
Nothing (yet)
7
+
- fix: performance improvements for setting breakpoints in large projects ([vscode#153470](https://github.com/microsoft/vscode/issues/153470))
0 commit comments