cpptools-srv2 taking up lots of time.

[mattijsjanssens]

Environment

• OS and Version: macOS Tahoe 26.6.1
• VS Code Version: 1.133.0
• C/C++ Extension Version: Microsoft C/C++ DevTools
• If using SSH remote, specify OS of remote machine:

Bug Summary and Steps to Reproduce

Bug Summary: C++DevTools in vscode seems to use cpptools-srv2 to parse the C++ files? This is already enough to almost hang my machine - has only 16Gb. Would be nice to get some

• warning about what it will do
• limit on memory? Limit on number of parallel compilations?

Configuration and Logs

{
    "configurations": [
        {
            "name": "Mac",
            "includePath": [
                "${workspaceFolder}/**"
            ],
            "defines": [],
            "compilerPath": "/usr/bin/clang",
            "cStandard": "c17",
            "cppStandard": "c++14",
            "intelliSenseMode": "macos-clang-arm64"
        }
    ],
    "version": 4
}

Other Extensions

No response

Additional context

No response

[MarijnKoesen]

I have the same, it's blasting full CPU constantly since an update earlier today.

[forrestjgq]

same issue, until I disabled cpp tools extention

[Colengms]

The cpptools-srv2 process parses files into the browse database (which supports several features). That behavior has not changed, just moved into a dedicated process (formerly done in the main cpptools process directly). Making full use of the CPU to accomplish that work as quickly as possible, is by-design.

You might try increasing the log level ("C_Cpp.loggingLevel": "Debug"), and monitoring the output, in case you're encountering an issue, such as parsing of files that shouldn't be parsed, following symlinks outside of your project folder, or perhaps repeatedly failing to parse the same file(s). If you're opening a huge repo (or root of an HD), you may want to isolate what is parsed using the browse.path field in a c_cpp_properties.json file, or the C_Cpp.default.browse.path setting.

[forrestjgq]

The cpptools-srv2 process parses files into the browse database (which supports several features). That behavior has not changed, just moved into a dedicated process (formerly done in the main cpptools process directly). Making full use of the CPU to accomplish that work as quickly as possible, is by-design.

You might try increasing the log level ("C_Cpp.loggingLevel": "Debug"), and monitoring the output, in case you're encountering an issue, such as parsing of files that shouldn't be parsed, following symlinks outside of your project folder, or perhaps repeatedly failing to parse the same file(s). If you're opening a huge repo (or root of an HD), you may want to isolate what is parsed using the browse.path field in a c_cpp_properties.json file, or the C_Cpp.default.browse.path setting.

Problem is:
My project is written by Python, it does NOT contain any c/cpp file, as well as CMakeList.txt, after updating to latest vsc, the cpp-tools just consumes too much CPU resource, what does it do? there is no reason I can think of.

[sean-mcmanus]

江国庆/Forrest (@forrestjgq) We have a potential fix pending for 1.34.0 -- 1.33.8 can try to parse extensionless files when it shouldn't. If you check your logging and see "Parsed file" logging that is most likely the cause.