Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dev Containers (RG) crawls all local files as soon as enabled - excessive CPU load #9586

Closed
spacerunner5 opened this issue Feb 24, 2024 · 2 comments
Labels
containers Issue in vscode-remote containers

Comments

@spacerunner5
Copy link

spacerunner5 commented Feb 24, 2024

As soon as enabled, the Dev Containers extension starts to crawl all subfolders of the current opened folder. This results in an excessive CPU usage.

No other extensions enabled.

Example on MacOS: Opening the root folder (MacHD) causes Dev Containers to crawl absolutely everything, even including mounted network shares. Identified on the Mac by looking at the rg processes launched after enabling Dev Container. Looking at the open files of the process, the crawling can be seen.

There are some reports around here and in other places stating that the Remote Development extension pack causes high CPU usage when enabled. This might be the cause. Disabling Dev Containers fixes the issue immediately after reload.

--

what did not help:

  • Dev Containers has the option of adding a "List of additional paths to search for repository configurations". Adding an entry there did however not change the behaviour.
  • Adding excludes to search didn't help.
  • Adding excludes to the watcher didn't help.

Any ideas?

I'm happy to provide more information.

--

  • VSCode Version: 1.86.2
  • Local OS Version: MacOS 13.6.4
  • Remote OS Version: not relevant
  • Remote Extension/Connection Type: Dev Container
@vscodenpa vscodenpa added the containers Issue in vscode-remote containers label Feb 24, 2024
@adlzanchetta
Copy link

I am facing the exact same issue in Linux (Ubuntu 22.04), same VSCode version (1.86.2).

Every time I start a Dev Container session my CPU usage goes to maximum. I have to open the terminal with an user with sudo powers, run the command top, get the PID of the two rg processes and kill them.

Killing these processes does not affect VSCode at all.

@chrmarti
Copy link
Contributor

chrmarti commented Apr 4, 2024

Fixing this in #9738

@chrmarti chrmarti closed this as completed Apr 4, 2024
@microsoft microsoft locked and limited conversation to collaborators May 19, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
containers Issue in vscode-remote containers
Projects
None yet
Development

No branches or pull requests

4 participants