After updating to the latest version of VS Code, the coding process has become extremely laggy, and memory usage spikes dramatically.

[lobmoo]

vscode 1.109.5
c/c++ 1.31.0
C/C++ Extension Pack 1.5.1
GitHub Copilot Chat 0.37.9
Remote Development 0.26.0

I’m developing on a Windows host and connecting to WSL (Ubuntu 20.04) using the Remote Development extension. After updating to the latest version of VS Code, I started experiencing severe lag, which significantly affects coding. So far, I’ve found that disabling either Copilot or the C/C++ extension can temporarily work around this issue.

[sean-mcmanus]

@chrmarti See also microsoft/vscode-cpptools#14241. We do not believe this is our C/C++ extension's bug. We have a Copilot hover feature which relies on the GitHub Copilot Chat extension.

[sean-mcmanus]

@chrmarti 3 users have reported that setting C_Cpp.copilotHover to "disabled" fixes it, and that causes vscodelm.selectChatModels to not be called, so we believe that VS Code function is causing the bug: https://github.com/microsoft/vscode-cpptools/blob/e08377a353f12c7575452a2226ff1fb93f6335ec/Extension/src/LanguageServer/Providers/CopilotHoverProvider.ts#L48.

The change we made that triggered this is the modelSelector that gets passed to selectChatModels at https://github.com/microsoft/vscode-cpptools/pull/14113/changes (the previous version triggered a failure of the feature).

[sean-mcmanus]

@chrmarti @lobmoo Our C/C++ extension has a (potential) fix for our next 1.32.0 pre-release at microsoft/vscode-cpptools#14327 -- via not calling the selectChatModels on every hover, although we still think it should be considered a bug with the selectChatModels API.

[lobmoo]

Thanks. I disabled hover for now, and it seems the leak is gone.

[sean-mcmanus]

@lobmoo FYI, you should only need to disable the C_Cpp.copilotHover and not C_Cpp.hover.

We discussed changing the default for C_Cpp.copilotHover to "disabled", but we went with the pending fix mentioned above instead.

[lobmoo]

收到 谢谢