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

Code Helper using ~100% CPU #39949

Closed
coreh opened this issue Dec 9, 2017 · 7 comments
Closed

Code Helper using ~100% CPU #39949

coreh opened this issue Dec 9, 2017 · 7 comments
Assignees
Labels
typescript Typescript support issues

Comments

@coreh
Copy link

coreh commented Dec 9, 2017

  • VSCode Version: 1.18.1
  • OS Version: 10.12.6

I'm getting "Code Helper" stuck at ~100% CPU

screen shot 2017-12-08 at 22 18 24

ps a~ $ ps aux | grep 65462
coreh            65462 100.0  1.7  3492052 281544   ??  R     5:33PM 128:06.61 /Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper.app/Contents/MacOS/Code Helper /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript/out/utils/electronForkStart.js /Users/coreh/Projects/zimboli/node_modules/typescript/lib/tsserver.js --useInferredProjectPerProjectRoot --enableTelemetry --cancellationPipeName /var/folders/m1/vk9trwwj3pz25vv0_jt7xtsc0000gn/T/vscode-tscancellation-da48568b3a6dd7891de0.sock* --locale en

Steps to Reproduce:

  1. Use VS Code for a suficiently long time (say, several hours) on a large enough project.
  2. A "Code Helper" process will start to use 100% CPU. Quitting VSCode does not terminate the Code Helper process, it needs to be killed from the Activity Monitor

Reproduces without extensions: Probably not (?)
(It doesn't trigger immediately, or consistently, but rather after several hours using the App, and I haven't been able to conclude if it will not trigger without extensions. However the ps output seems to indicate that the offending file is /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript/out/utils/electronForkStart.js, so it's the built in TypeScript extension?)

Thanks in advance!

@vscodebot vscodebot bot assigned mjbvz Dec 9, 2017
@vscodebot vscodebot bot added the typescript Typescript support issues label Dec 9, 2017
@bestvow
Copy link

bestvow commented Dec 9, 2017

igore files such as
/**/node_modules

@coreh
Copy link
Author

coreh commented Dec 11, 2017

@bestvow Wouldn't that break type checks, autocomplete and "Jump to Definition" for the modules within node_modules?

@bestvow
Copy link

bestvow commented Dec 11, 2017

@coreh Would you like to show me your extensions?

@mjbvz
Copy link
Collaborator

mjbvz commented Dec 11, 2017

This issue was moved to microsoft/TypeScript#20630

@mjbvz mjbvz closed this as completed Dec 11, 2017
@baotongw
Copy link

baotongw commented Dec 12, 2017

it also happened in normal javascript, after I open 10+ files, the cpu cost increased rapidly.

VsCode version: 1.18.1
mac os: 10.12.6

@acomito
Copy link

acomito commented Dec 25, 2017

Code helper was going crazy almost 100% of the time I had VScode open (CPU at 60%-100%). My current working hypothesis is it was https://github.com/wix/import-cost which I started using (I think) when I tried out https://burkeknowswords.com/introducing-react-food-truck-b23ea1e2cf79

Disabling import-cost seems to bring code helpers CPUs way down (averaging around 12-20%). Then enabling it again brings me back up around (at least) 50% for code helper.

further reading: wix/import-cost#35

@r-i-c-h
Copy link

r-i-c-h commented Dec 31, 2017

Disabling the Import-Costs package seems to have cleared up my CPU issues with Code Helper.
Thanks all for the info.

@vscodebot vscodebot bot locked and limited conversation to collaborators Jan 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
typescript Typescript support issues
Projects
None yet
Development

No branches or pull requests

6 participants