Help!!! huge (>10 GB) RAM usage after enabling the extension

[kunchuf]

Hello everyone, Good day to you,

The RAM usage peaks when cpptools is enabled in vscode.

Below is the usage when extension is not enabled:

2GB after few minutes:

6GB now, and it keeps on eating (my precious) RAM

And 10GB!!!

vscode details:

Version: 1.66.0 (user setup)
Commit: e18005f0f1b33c29e81d732535d8c0e47cafb0b5
Date: 2022-03-30T05:50:14.623Z
Electron: 17.2.0
Chromium: 98.0.4758.109
Node.js: 16.13.0
V8: 9.8.177.11-electron.0
OS: Windows_NT x64 10.0.19042

the cpp tools version is v1.9.7:

I tried limiting the C_Cpp: Max Memory and other similar settings, which didn't make any change in the behaviour.

Any help appreciated!!

[michelleangela]

@kunchuf
Could you check if this repros on previous release version https://github.com/microsoft/vscode-cpptools/releases/tag/1.8.4?

Does this also reproduce on a simple project with one small source file or is a large project required to reproduce this?

Could you provide logs of the language server for the case its using a lot of memory (see https://code.visualstudio.com/docs/cpp/enable-logging-cpp#_enable-logging-for-the-language-server)?

[kunchuf]

Hello @michelleangela

Thanks for taking up this issue! I tried all three of your suggestions.

1. Using previous release version - v1.9.2 has the same problem. where do I get the vsix file for v1.8.4? It is not listed under version history in marketplace.
   
2. On simple project - The extension behaves well on project with few 100s of files. The problem is on a workspace with the humongous number of files.
3. Debug logs attached, but I replaced the actual file names/paths with something else. (Sorry, can't reveal it). Let me know if something else is needed.
   log_c_ext.log
   At some point (around 1 or 2 GB of RAM usage) the output console stopped printing debug logs, but the RAM usage kept increasing.

[michelleangela]

Other versions of the extension can be installed from the VS Code client, from the extensions panel.

Click on the settings icon of the extension and then select "Install Another Versions..."

[kunchuf]

@michelleangela
The last good one is v1.7.1!!! The RAM usage caps at about 300MB. And I see that the debug logs don't get stuck as in other versions.

[michelleangela]

Note: I created a bug report for this at #9181 to continue the investigation and discussion of this issue.