Skip to content
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

Extension causes high cpu load #3334

Closed
arinzejustin opened this issue Nov 28, 2021 · 6 comments
Closed

Extension causes high cpu load #3334

arinzejustin opened this issue Nov 28, 2021 · 6 comments

Comments

@arinzejustin
Copy link

arinzejustin commented Nov 28, 2021

  • Issue Type: Performance
  • Extension Name: vscode-docker
  • Extension Version: 1.18.0
  • OS Version: Windows_NT x64 10.0.10240
  • VS Code version: 1.62.3

⚠️ Make sure to attach this file from your home-directory:
⚠️c:\Users\<name>\AppData\Local\Temp\ms-azuretools.vscode-docker-unresponsive.cpuprofile.txt

Find more details here: https://github.com/microsoft/vscode/wiki/Explain-extension-causes-high-cpu-load

@bwateratmsft
Copy link
Collaborator

bwateratmsft commented Nov 29, 2021

@arinzejustin can you add the cpuprofile file?

It's worth mentioning, sometimes CPU usage spikes for no apparent reason and VSCode blames the extension.

@rcjsuen
Copy link
Contributor

rcjsuen commented Dec 9, 2021

I wonder if this is related to #3347. 🤔

@bwateratmsft
Copy link
Collaborator

@rcjsuen Do you know if the language server gets launched in the same process? If not, I would suspect that this is not due to #3347, though I'm not entirely sure what conditions trigger VSCode to suggest filing these issues.

@rcjsuen
Copy link
Contributor

rcjsuen commented Dec 9, 2021

Do you know if the language server gets launched in the same process?

I believe this is the code so it looks like it calls child_process.spawn(...).

@bwateratmsft
Copy link
Collaborator

Ok. So it's unlikely but still possible that VSCode is tracking the CPU usage of those child processes and associating it back to the extension that spawned it.

Also I see this in the process explorer, so it's definitely a separate process:
image

@AzCode-Bot
Copy link
Collaborator

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!

@microsoft microsoft locked and limited conversation to collaborators Feb 9, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants