microsoft / microsoft/vscode-remote-release

Extremely High CPU Usage with rg process spawns

Open
#11,283 4 comments 2 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

Dominant language
Dockerfile
Stars
4.2k
Forks
469
Avg merge
1d 1h
Merged PRs (30d)
1

Description

  • VSCode Version:
    Version: 1.105.1 (user setup)
    Commit: 7d842fb85a0275a4a8e4d7e040d2625abbf7f084
    Date: 2025-10-14T22:33:36.618Z
    Electron: 37.6.0
    ElectronBuildId: 12502201
    Chromium: 138.0.7204.251
    Node.js: 22.19.0
    V8: 13.8.258.32-electron.0
    OS: Windows_NT x64 10.0.26100
    // Dev Containers v0.427.0

  • Local OS Version: N/A

  • Remote OS Version: Ubuntu Linux Server 24.04 LTS

  • Remote Extension/Connection Type: Dev Containers

CPU usage spikes on a bunch of rg processes when a Dev Container is launched for a docker container. There is relatively low CPU usage even when the docker container is just running using a -ti command in the terminal, but as soon as you attach a dev container to it and open it, 12+ CPU cores are pinned at ~100% with some rg processes. This seems similar to the issues discussed here: https://github.com/microsoft/vscode-remote-release/issues/9586 & https://github.com/microsoft/vscode/issues/206482

I attempted to go back to releases of dev containers both a few versions back from latest and near when these issues were stated to be solved with no luck on a fix. Since this was being used mainly on an AWS EC2 image with CIS STIG hardened Ubuntu AMI, I attempted to reproduce locally on my windows/WSL machine and the same issue occurred with the same amount of CPU pinning.

Steps to Reproduce:

  1. Run a docker container
  2. Attach to dev containers
  3. Watch CPU usage pin to 100

Does this issue occur when you try this locally?: Yes
Does this issue occur when you try this locally and all extensions are disabled?: Yes

Image

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.