"Code Helper" uses too much CPU on macOS

[mvolkmann]

I know this has been reported and the issues have been closed several times. But the issue is not fixed. I really love VS Code, but I might have to stop using it because it drags my machine down too much.

Why are there sometimes multiple "Code Helper" processes running? I have 10 running at the moment.

Why don't all the "Code Helper" processes stop running when VS Code is exited?

Why do they frequently use more than 70% CPU even when VS Code is running, but not being used?

[mjbvz]

Please follow these instructions to collect performance information. Start by sharing the output of code-insiders --status

[proton1k]

I'm subscribing for the issue, have the similar situation when open a second VSCode window and hit save button. I am highly certain it's indeed a plugin like Emmet which performs tree-shaking logic to show suggestions (like autocomplete). I will init the suggested profiling if I will encounter it again, but really would be great to know if there's a memory leak or something else...

update
I guess the main thread here is the main, but it's limited for commenting to maintainers.

[danrosenthal]

I was experiencing the same issues. I tracked this down to a runaway process called electron_node tsserver.js using Help > Process Explorer. Nuking my node_modules directory and re-installing seems to have fixed the problem for me. CPU load back to a normal range and my laptop no longer sounds like it's ready for liftoff.

[egamma]

Pls follow this guide https://github.com/microsoft/vscode/wiki/Performance-Issues when reporting performance issues.

[danrosenthal]

Thank you @egamma, I have submitted the issue here: #74854

[proton1k]

Thanks @danrosenthal and @egamma, unfortunately I can't reproduce my case. Will close current thread. Oh, I can't do that. Please close the thread.

[egamma]

@o1dnik you cannot close the issue since you are not the original reporter.

@mvolkmann we need more information to track this issue down. CodeHelper process should terminate when VS Code is exited. So we need to know what kind of processes are sticking around. If you can let us know the command line arguments from the processes when this happens, then this would be really helpful.

[mvolkmann]

Sorry for the delay in responding. After having this issue for a couple of months, it hasn't happened in the last two days. Give me a few more days to see if it comes back. If it does then I'll follow the instructions for reporting performance issues and report my findings. Otherwise I'll close this issue.

…

On Wed, Jun 5, 2019 at 1:28 AM Erich Gamma ***@***.***> wrote: @o1dnik <https://github.com/o1dnik> you cannot close the issue since you are not the original reporter. @mvolkmann <https://github.com/mvolkmann> we need more information to track this issue down. CodeHelper process should terminate when VS Code is exited. So we need to know what kind of processes are sticking around. If you can let us know the command line arguments from the processes when this happens, then this would be really helpful. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#74755?email_source=notifications&email_token=AAATLUG2MMLDAUBHJGWG7MLPY5MHHA5CNFSM4HSDCLEKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODW6XGUI#issuecomment-498955089>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAATLUBFVB2FXMWEIIEIRX3PY5MHHANCNFSM4HSDCLEA> .

-- R. Mark Volkmann Object Computing, Inc.

[mvolkmann]

[mvolkmann]

code-status.txt

[mvolkmann]

[mjbvz]

Now being tracked in this issue #74960