-
Notifications
You must be signed in to change notification settings - Fork 285
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
Labels
containers
Issue in vscode-remote containers
Comments
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 Killing these processes does not affect VSCode at all. |
11 tasks
This was referenced Apr 2, 2024
Fixing this in #9738 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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:
Any ideas?
I'm happy to provide more information.
--
The text was updated successfully, but these errors were encountered: