-
Notifications
You must be signed in to change notification settings - Fork 309
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
File watcher maxes CPU when folder contains symlink loop #4818
Comments
Turns out I have symlink directory loop in one of the folders I was connecting to with "Remote - WSL":
and when I click "Reconnect" after getting the "Cannot Reconnect" dialog after resuming from hibernation, I get several (Full path: I attached a debugger to one of these processes, and in devtools, file:
which would seem to indicate that a symlink directory loop is being followed infinitely. Certainly, this doesn't happen on any other folder/repo/project. |
Also, shouldn't files that are excluded from search be excluded by the file watcher? |
@bpasero FYI, also see question #4818 (comment) |
If one of our watchers fails over circular symbolic links, I suggest to report this as issue to the watcher in use. I am not sure which watcher we end up using in remote setups. If a watcher fails to exclude a directory, even though indicated by settings, please file an issue in https://github.com/Microsoft/vscode/ with clear steps how to reproduce. Note that if |
Following instructions from https://stackoverflow.com/a/48214059/535071, I profiled a rogue
bootstrap-fork --type=watcherService
and recorded a CPU profile: CPU-20210331T105942.zipThe top 8 rows by CPU time:
chokidar - npm
paulmillr/chokidar: Minimal and efficient cross-platform file watching library
Originally posted by @drkvogel in #3126 (comment)
The text was updated successfully, but these errors were encountered: