vscode: vscode become 10x slower when i updated to version 1.74.1

Many developers accross our organization are also hitting extreme slowdowns with 1.74.x after updating from Typescript 4.6.4 to 4.7.4 and Angular from 13.x.x to 14.x.x. This does not occur when the same updates are done and 1.73.x is used. These slowdowns are most apparent with Intellisense and errors being denoted/clearing. However, slowdowns have also been reported in actions such as renaming functions and variables via the “Rename Symbol” functionality.

In an attempt to give you as much information as possible - I have went through the comments on this thread and have attempted to answer all of your questions. A couple of the answers that I found below will allow us to work effectively - but I still wanted to share my findings.

• Current version
  • 1.74.3
• Do I have extensions.experimental.useUtilityProcess enabled?
  • No
• Do I have window.experimental.useSandbox enabled?
  • No
• Do I have “Screen Reader Optimized” in the status bar?
  • No
• Problem occurs with all extensions disabled?
  • Yes - there may be a slight speedup compared to when they are enabled, but there is still a noticeable slowdown
• Could you please follow the steps described here and share CPU profiles of the renderer and the extension host processes
  • extension-host-process.cpuprofile.txt renderer-process.cpuprofile.txt
• Could you please share the window and extension host logs

Window

2023-01-11 14:13:03.090 [warning] Settings pattern "keyboard.*" doesn't match any settings
2023-01-11 14:13:04.975 [error] RequestService#request (browser) - error https://bingsettingssearch.trafficmanager.net/api/Search {}
2023-01-11 14:13:04.975 [info] Setting search error: XHR failed
2023-01-11 14:13:04.983 [error] RequestService#request (browser) - error https://bingsettingssearch.trafficmanager.net/api/Search {}
2023-01-11 14:13:04.983 [info] Setting search error: XHR failed
2023-01-11 14:13:05.127 [warning] Settings pattern "keyboard.*" doesn't match any settings
2023-01-11 14:13:05.875 [error] RequestService#request (browser) - error https://bingsettingssearch.trafficmanager.net/api/Search {}
2023-01-11 14:13:05.876 [info] Setting search error: XHR failed
2023-01-11 14:13:05.926 [error] RequestService#request (browser) - error https://bingsettingssearch.trafficmanager.net/api/Search {}
2023-01-11 14:13:05.927 [info] Setting search error: XHR failed
2023-01-11 14:13:06.022 [warning] Settings pattern "keyboard.*" doesn't match any settings
2023-01-11 14:13:06.872 [error] RequestService#request (browser) - error https://bingsettingssearch.trafficmanager.net/api/Search {}
2023-01-11 14:13:06.872 [info] Setting search error: XHR failed
2023-01-11 14:13:06.949 [error] RequestService#request (browser) - error https://bingsettingssearch.trafficmanager.net/api/Search {}
2023-01-11 14:13:06.949 [info] Setting search error: XHR failed
2023-01-11 14:13:07.038 [info] [perf] Render performance baseline is 44ms
2023-01-11 14:13:07.234 [warning] Settings pattern "keyboard.*" doesn't match any settings
2023-01-11 14:13:07.936 [error] RequestService#request (browser) - error https://bingsettingssearch.trafficmanager.net/api/Search {}
2023-01-11 14:13:07.937 [info] Setting search error: XHR failed
2023-01-11 14:13:07.937 [error] RequestService#request (browser) - error https://bingsettingssearch.trafficmanager.net/api/Search {}
2023-01-11 14:13:07.938 [info] Setting search error: XHR failed

Extension

2023-01-11 14:13:04.586 [info] Extension host with pid 15752 started
2023-01-11 14:13:04.586 [info] Skipping acquiring lock for c:\Users\Trevor.Burch\AppData\Roaming\Code\User\workspaceStorage\5bbaac8d07f6bf7303e0148468c75868.
2023-01-11 14:13:04.634 [info] ExtensionService#_doActivateExtension vscode.microsoft-authentication, startup: false, activationEvent: 'onAuthenticationRequest:microsoft'
2023-01-11 14:13:04.635 [info] ExtensionService#_doActivateExtension vscode.git-base, startup: true, activationEvent: '*', root cause: vscode.git
2023-01-11 14:13:04.635 [info] ExtensionService#_doActivateExtension vscode.npm, startup: true, activationEvent: 'workspaceContains:package.json'
2023-01-11 14:13:04.679 [info] ExtensionService#_doActivateExtension vscode.git, startup: true, activationEvent: '*'
2023-01-11 14:13:04.680 [info] ExtensionService#_doActivateExtension vscode.github, startup: true, activationEvent: '*'
2023-01-11 14:13:04.819 [info] ExtensionService#_doActivateExtension vscode.github-authentication, startup: false, activationEvent: 'onAuthenticationRequest:github'
2023-01-11 14:13:05.026 [info] Eager extensions activated
2023-01-11 14:13:05.101 [info] ExtensionService#_doActivateExtension vscode.debug-auto-launch, startup: false, activationEvent: 'onStartupFinished'
2023-01-11 14:13:05.102 [info] ExtensionService#_doActivateExtension vscode.emmet, startup: false, activationEvent: 'onStartupFinished'
2023-01-11 14:13:05.102 [info] ExtensionService#_doActivateExtension vscode.merge-conflict, startup: false, activationEvent: 'onStartupFinished'
2023-01-11 14:13:05.102 [info] ExtensionService#_doActivateExtension ms-vscode-remote.remote-wsl-recommender, startup: false, activationEvent: 'onStartupFinished'
2023-01-11 14:13:05.689 [info] ExtensionService#_doActivateExtension vscode.configuration-editing, startup: false, activationEvent: 'onLanguage:jsonc'
2023-01-11 14:13:05.690 [info] ExtensionService#_doActivateExtension vscode.json-language-features, startup: false, activationEvent: 'onLanguage:jsonc'
2023-01-11 14:13:05.690 [info] ExtensionService#_doActivateExtension vscode.typescript-language-features, startup: false, activationEvent: 'onLanguage:jsonc'

• “Our Angular 14 project uses TypeScript v4.8.4, as @angular/compiler-cli@14 does not support TypeScript v4.9.4”

  • I did confirm that setting VSCode to use the “Workspace Version” of 4.7.4 instead of the built in 4.9.4 does resolve the slowdown

• “Version 1.74.2 on Windows is very slow, the Mac version looks good.”

  • We are also seeing this - the slowdown only seems to be happening on Windows and not Mac
• Does this also reproduce using insiders?
  • I do not see the slowdown when using 1.75.0-insider

So we discovered the problem related with TypeScript:

Our Angular 14 project uses TypeScript v4.8.4, as @angular/compiler-cli@14 does not support TypeScript v4.9.4:

VSCode v1.74.x comes with TypeScript v4.9.4 by default, causing this issue:

By telling VSCode to use the same TypeScript version as the workspace (v4.8.4), the slowness disappears.

For this change to be applied on all workspaces, add this to the user settings: "typescript.tsdk": "node_modules\\typescript\\lib"

My whole project team and I also have performance issues, even when all extensions are disabled. We have downgraded to VS Code 1.73, using this version there are no performance issues.

VS Code Version: 1.74.1 OS: Windows 10 21H2 Language of project: TypeScript (Angular 14) Problem occurs with all extensions disabled: Yes Problem Description: IntelliSense, TypeScript linting (VS Code native) and file save are heavily delayed

We’re with the exact same problem with TypeScript (Angular 14). On VSCode 1.73.1 the issue doesn’t occur. After updating to 1.74.x everything becomes slow: IntelliSense, linting, etc.

Version: 1.74.1 (system setup)
Commit: 1ad8d514439d5077d2b0b7ee64d2ce82a9308e5a
Date: 2022-12-14T10:30:51.966Z
Electron: 19.1.8
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Windows_NT x64 10.0.19044
Sandboxed: No

My whole project team and I also have performance issues, even when all extensions are disabled. We have downgraded to VS Code 1.73, using this version there are no performance issues.

VS Code Version: 1.74.1 OS: Windows 10 21H2 Language of project: TypeScript (Angular 14) Problem occurs with all extensions disabled: Yes Problem Description: IntelliSense, TypeScript linting (VS Code native) and file save are heavily delayed

Me too, I write TypeScript with prettier and eslint extensions and have had quite a bit of difficulty with performance. I don’t remember the version, but it is recent.

• The red wavy line indicating an error does not change for more than a minute after changing the code.
• The round icon indicating unsaved does not change for about 10 seconds after saving (command + S).

Version: 1.74.1 (Universal)
Commit: 1ad8d514439d5077d2b0b7ee64d2ce82a9308e5a
Date: 2022-12-14T10:33:40.793Z (4 days ago)
Electron: 19.1.8
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Darwin x64 21.6.0
Sandboxed: No

@jpike88 I understand your frustration but we can only fix issues that we can reproduce. For that we depend on the information you deliver.

At the high level view there is a process that executes all extension code. That’s the extension process. There is also the renderer process which is in charge of the UI. With this architecture extensions cannot directly crash or freeze the renderer. Extensions, however, can negatively impact each other and that’s outside our control. Also, extensions can “death-hug” us by responding with too much data. Now, to bring in some structure and info try any or all of the below steps

• Slow extensions results? Use the following tools that come with VS Code.
  • “F1 > Show Running Extensions” and check for extension annotated with a warning. Those have caused freezes on the extension host process
  • “F1 > Show Logs > Window” and check for messages like "UNRESPONSIVE extension host: "
  • Enable trace logging (“F1 > Set Log Level > Trace”) and check the extension host log (“F1 > Show Logs > Extension Host”) for respective operations, like [SOME_EXT] INVOKE provider ‘he=>he.provideHover(c.URI.revive(H),Q,Y)’ and [SOME_EXT] provider DONE after 1ms
  • Run bisect (“F1 > Start Extension Bisect”) and try to identify a noisy neighbour extension
• Frozen/crashed renderer ? This is really serve and should absolutely not happen. We do some automating profiling and reporting when this happens but we really need some steps. If you have some you can profile the renderer process as explained here https://github.com/Microsoft/vscode/wiki/Performance-Issues#profiling-the-renderer-process

Thanks for helping us

So far I think people experience this in Python and TypeScript extension is that accurate? Or what exact extensions are involved here and what kind of actions feel slower? Would be interesting to reproduce on our end.

Using on TypeScript development here. This happens with or without extensions.

Actions that feel slower: IntelliSense suggestions take ages to appear; Imports take ages to be acknowledged, as if the import of the class/whatever was not made; Errors on the code take ages to appear/disappear;

I’ve downgraded do 1.73.1 so I cannot send logs for now as I’m using VSCode for work. I’ll send them as soon as I can.

@bpasero i don’t use any extensions for javascript or typescript. No problem I will provide details for that comment later maybe tommorow itself.

@bpasero extensions.experimental.useUtilityProcess was enabled, window.experimental.useSandbox wasn’t. I have disabled extensions.experimental.useUtilityProcess and restarted VSCode and the issue persists.

I’m experiencing the same issue with v1.74.* with no extensions enabled. I even opened an issue , but close it, because after I updated to the latest version everything was fine in the first couple of seconds. I will downgrade as suggested above. EDIT: I can confirm that after downgraded to 1.73, VSCode have no performance issues and everything is responding instantly.

I want to chime in and say I’m experiencing the same really slow performance, especially with Intellisense on 1.74.2. I downloaded 1.73.1, and Intellisense is much faster than 1.74.2.

Are there any debug logs we can take a look at to see where things are slow in VSCode, like perhaps maybe one of my installed extensions is buggy, or if it’s VSCode itself?