-
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
cpu usage 100% #594
Comments
Update:
|
1, is it possible to share that simple source file, let me try? // or let me do a guess, was that src file put in a symlink folder? |
I'm also seeing high CPU usage from this plugin the past few days. |
@ZiYang-oyxy @BlaineEXE sorry to hear but thank you for reporting this. I'm very curious what is causing this. Can you try upgrading to the latest extension (1.19.0) and see if you can reproduce this? If you can, are you able to change the bashIde setting |
The bug is fixed after I upgrade to from 3.3.1 to 4.0.1. I'll watch for a few days to make sure the bug is fixed. |
Thanks! I'll close this for now, please reopen if you experience issues related to high CPU usage. |
Note that 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. |
bash-language-server version: Version is 3.3.1
node version: v18.12.1
mac os version: macOS 13.0.1 (22A400)
ps
command output:mac
sample
command output:It looks like nested dead loops from the call trace
The text was updated successfully, but these errors were encountered: