-
Notifications
You must be signed in to change notification settings - Fork 131
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
High CPU utilization #238
Comments
@m1keil Thank you for the report. From my experience with fixing the previous CPU-related bug it would be helpful to have access to the file which the completion was requested in and the position where it was requested. I don't seem to have access to the screencast, but providing it as copy-paste-able text would be incredibly helpful either way, so I can try to reproduce it without having to retype anything. FWIW you can also encrypt any sensitive data via PGP using our key: https://www.hashicorp.com/security#secure-communications |
The attached CPU profile suggests the hot codepath is the same, or very similar - i.e. it is caused by a config which the parser isn't able to parse for some reason, but I can't tell what the config is or what the reason may be without more data unfortunately. |
Hey @radeksimko, |
I believe I managed to create a small test case.
where
and
The bug gets triggered when editing in |
Reproduced - thank you! I will look into this. |
@radeksimko I am also seeing high CPU again - same as in #217. I can't say if its the same as this issue as I tend to jump around files a lot so hard to pin down. I have attached log and CPU files as before in case its useful. |
@jamesskinner I was able to reproduce that one as well and I think it is the same bug which can also be addressed by #239 - at least the CPU wasn't spiking with a custom build with that patch. |
Bug fix was shipped in Please let me know if you continue having CPU or any other problems by opening a new issue. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Looks like a similar one to #217, #230
I've tried to provide a simple case but was unable to recreate. My workspace contains multiple modules and Terraform project.
Server Version
Terraform Version
Client Version
VSCode
Expected Behavior
terraform-ls
to not get stuck on 100%.Actual Behavior
terraform-ls
gets stuck on 100% cpu utilization until killed.Screencast
I've recorded this as a screencast
The actual behavior is triggered manually by me calling for auto complete ("Trigger Suggest" in VSCode - Ctrl + Space).
CPU Profile
cpu.prof.zip
The text was updated successfully, but these errors were encountered: