-
-
Notifications
You must be signed in to change notification settings - Fork 88
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
ExtensionHost CPU usage goes up to 100% when enabling this extension #185
Comments
I am experiencing the same behavior. Disabling the extension returns the CPU usage to normal. |
Is it high for startup or all the time? |
At all the time 🙃 |
I am developing the extension on Windows 10 with WSL2 and my extension_host CPU usage is zero when idle. |
I'm on MacOS 11.0.1. It stays at 100% until the extension is disabled. |
Hello guys I have the same issue. 100% CPU usage when this extension is enabled. I have disabled the extension for now. Let me know when this issue is fixed cause I like this extension. Cheers! |
@tonix-tuft Are you on MacOS? |
@ecmel Yes. |
Can be related to paulmillr/chokidar#447 |
@felipekb @davisben @tonix-tuft Could you please try version 1.1.4? |
OK |
For reference Windows 10 with WSL 2:
|
I don't know man, this is what I see on my Mac, something you can advise me to try in order to help further troubleshoot this issue? |
I'm still seeing 100% with 1.1.4. |
@davisben Same for me. |
@felipekb Are you on OS X? |
@davisben @tonix-tuft Can you please try with |
same here MacOs Catalina 10.15.7 |
@tonix-tuft Yes, Im running OS X 11.0.1 |
@ecmel OK, it works with Is there a way to disable this extension on a per-file basis? E.g. like Prettier does with I have a huge HTML file with some dumped data, maybe it's because of that... |
@tonix-tuft Where is your CSS? Are you using local or remote css? If remote then you dont have to enable watch setting |
@ecmel It's local. |
@tonix-tuft You can enter absolute file names to
|
The same started happening to me today after the recent update of VScode (current version is 1.52.0). Setting Also, I had this previously:
and it was still up to 300% CPU usage if that's helpful. I'm on macOS 11.0.1. |
How can I do this on a per-project basis? Can I put it in a project's |
@tonix-tuft Yes |
Confirming that pegged processor is resolved with setting
All source files are local... |
I have the same problem, on a MacBook Pro Catalina, VScode Insiders, CPU usage 100% when this extension is enabled :( |
Upstream bug reports: paulmillr/chokidar#859 All seems to be resolved. Will open a new issue. |
Anybody tried 1.1.6? |
Just restarted the computer for unrelated reasons. Tried re-enabling OSX: I know, it's not easy to diagnose and resolve someone else's issues asynchronously, but I do appreciate the effort you've put into creating/maintaining this extension and for looking into this issue. In the big picture, it's not a big deal because there's at least a means to mitigate the issue for now by disabling |
Could it be related to VS Code's |
Possible but doubtful because I reverted to 1.51 to test and it still happened for me. That said, in theory 1.52 could have introduced new/changed user settings that contribute to this issue and reverting to 1.51 would therefore not undo that. |
Fixed in 1.2.0 |
No more |
Yes because there is no directory watcher. You can specify local and remote css files in a new settings (per workspace folder) |
OK, so I if I have just updated the extension to 1.2.0 and I don't see CPU spikes anymore I am good to go, right? :) |
Looks good now, thanks a lot!! |
I've noticed that the CPU usage with this extension increases the CPU usage by a lot.
Tested by disabling it, got average numbers after that.
Here's the output of running
code --status
.The text was updated successfully, but these errors were encountered: