Use vscode-nsfw watcher
See original GitHub issueI’m seeing very high CPU usage when running code-server on my Mac Pro (SSD disk). I run it in a project root that contains all my projects, which have lots of node_modules files etc. This high CPU usage continues even when not doing anything with code-server / VSCode for a long time.
Version
code-server
version: 1.31.1-100- OS Version: darwin-x64 node-v8.9.3
Steps to Reproduce
- Run code-server on Mac in project root (lots of projects under it)
- Open code-server in two Chrome browser windows (on a Windows computer)
- Observe high continuous CPU usage
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:10 (4 by maintainers)
Top Results From Across the Web
vscode-nsfw - npm
A simple file watcher for Node. Latest version: 2.1.8, last published: a year ago. Start using vscode-nsfw in your project by running `npm...
Read more >vscode-nsfw examples - CodeSandbox
Learn how to use vscode-nsfw by viewing and forking vscode-nsfw example apps on CodeSandbox. ... AboutA simple file watcher for Node952Weekly Downloads.
Read more >Use vscode-nsfw watcher · Issue #132 · coder/code-server
I'm seeing very high CPU usage when running code-server on my Mac Pro (SSD disk). I run it in a project root that...
Read more >NSFW - Node Sentinel File Watcher | Axosoft GitKraken
A super fast and scaleable file watcher that provides a consistent interface on Linux, OSX and Windows.
Read more >VSC unable to watch for file changes in this large workspace ...
I just started using VSCode version 1.24.1 ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The subprocesses taking all the CPU seem to be the ones with these parameters:
13819 kennu code-server --bootstrap-fork vs/workbench/services/files/node/watcher/unix/watcherApp --args ["--type=watcherService"] --data-dir /Users/kennu/.code-server
14132 kennu code-server --bootstrap-fork vs/workbench/services/files/node/watcher/unix/watcherApp --args ["--type=watcherService"] --data-dir /Users/kennu/.code-server
(They also include a long --env parameter but I removed it from here.)
Ah wonderful. We’ll be able to fix this for sure!
There’s an issue regarding this on vscode as well: https://github.com/Microsoft/vscode/issues/3998