-
Notifications
You must be signed in to change notification settings - Fork 132
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
server.js has high CPU usage on MacOS #638
Comments
Thanks for reporting this. I'm puzzled and would love to figure out what is going on. Can you share some output from the extension (View -> Output -> Bash IDE) while this is ongoing? |
Is the high CPU usage only when the extension starts, while typing or also when inactive? And does it change anything if you open a small workspace with few files compared to opening a large workspace (e.g. home directory)? |
@BlaineEXE Do you have shellcheck installed? A new version [email protected] has just been released, introducing a short execution delay and debouncing for ShellCheck tasks. Let me know if the new version works for you. |
Just was able to test this, I'm still seeing the issue.
|
Thanks. Not sure if you saw the previous questions, but it would be helpful if you have time to answer them: #638 (comment) Do you have shellcheck installed? |
I can reproduce high CPU usage if I open a workspace for a sub folder with many files, like my home folder. |
Apologies. I was hasty. I have shellcheck 0.9.0 installed; the latest. I have 3 projects with many bash scripts in them. If I close all shell script files in all workspaces, I still see the high CPU usage. |
|
We have fixed a bug causing memory leaks and high CPU usage for workspaces with many files – this has been released as [email protected] and the vscode extension 1.26.0. Can you confirm that this solves the issue for now? |
Seems to be fixed now. Thanks! 🙏 |
Thanks for testing this! |
I'm seeing server.js have very high CPU usage on MacOS. It's reportedly using 2.5 CPU cores on my 6-core i7 processor.
The text was updated successfully, but these errors were encountered: