microsoft / microsoft/vscode-cpptools

Excessive CPU usage with https://github.com/dotnet/runtime

Open
#7,115 8 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

investigate: repro Language Service Not Repro - Internal performance
Dominant language
TypeScript
Stars
6.2k
Forks
1.7k
Avg merge
14h 46m
Merged PRs (30d)
61

Description

I'm experiencing this in my linux development VM for https://github.com/dotnet/runtime, running a VS Code client on Windows connected to the linux host (so cpptools runs on the linux host along with some node processes, while the UI runs outside of the linux host). Has any testing happened with that repo for this issue? It does seem to be much worse during builds, which is confusing because I got the impression that vscode takes gitignore into account for these things like it does for project-wide search and build artifact directories are ignored.

When I checked in and opened top, cpptools' cpu time total was around 65 hours, with xorg and konsole at 23 and 21 hours and node (probably the cpptools parent?) at 19. cpptools also was using about half a gig of memory (2.4g virtual).

Originally posted by @kg in https://github.com/microsoft/vscode-cpptools/issues/5574#issuecomment-791321351

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file, test, or code entry point is named. Start by reproducing the Linux development-VM setup with VS Code connected from Windows, then observe cpptools and node CPU usage during builds. Done means identifying the cause of the excessive CPU use and verifying that usage is reduced in the reported workflow.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, linux, nodejs, typescript, vscode
Domain
developer-experience, performance, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.