code helper high CPU
log:
➜ ~
➜ ~ ps aux | grep 4532
macbook 4532 114.1 12.1 4722660 1014916 ?? R 7:02下午 23:50.65 /Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper.app/Contents/MacOS/Code Helper /Applications/Visual Studio Code.app/Contents/Resources/app/out/bootstrap --type=searchService
root 237 0.0 0.1 2453276 9876 ?? Ss 9:09上午 0:00.21 /usr/libexec/thermald
macbook 4985 0.0 0.0 2432804 1716 s000 R+ 7:22下午 0:00.00 grep --color=auto --exclude-dir=.bzr --exclude-dir=CVS --exclude-dir=.git --exclude-dir=.hg --exclude-dir=.svn 4532

Can you include more details? Does it happen consistently? Did you use search or cmd+p before this? Other steps to reproduce?
I have also encountered this problem. it happen consistently. I can give you the process report created by MacBook Pro
A process profile will probably just tell us that it's doing something in JS which isn't that useful. Did you use search or cmd+p before this? Other steps to reproduce?
This issue has been closed automatically because it needs more information and has not had recent activity. Please refer to our guidelines for filing issues. Thank you for your contributions.
I'd like to reopen this issue. After the latest update, I'm seeing this all the time.
The steps to reproduce would be:
I've disabled all of the extensions that I have installed, but these are the one's I'm using
$ code --list-extensions --show-versions
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
@gtb104 Is this 1.13.0? Which OS? What are the command line arguments of the process?
My Code version is 1.13.1, the code helper problem also seem at this version, it's memory usage also very high, almost 1.4GB! The OS is macOS 10.12.2.
@xiaomoer What are the command line arguments of the process?
This issue has been closed automatically because it needs more information and has not had recent activity. Please refer to our guidelines for filing issues. Thank you for your contributions.
it happen consistently
@wuliupo Could you open a new issue and include the command line arguments of the process? Also check if it still occurs with extensions turned off (Launch with code --disable-extensions). Thanks.
I've recently updated to 1.13.1 and it seems to be much better. I'm on OSX 10.11.5. Don't know about the command line args. I always start it from my Dock.
What I've noticed is that, even after closing VS Code, there are still some instances of Code Helper hanging around that are consuming upwards of 100+ % CPU.
@chrmarti I have the same problem, here are the command line arguments:
$ pgrep -lf 'Code Helper'
28505 /Users/wmertens/Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper.app/Contents/MacOS/Code Helper /Users/wmertens/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript/out/utils/electronForkStart /Users/wmertens/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js --useSingleInferredProject --enableTelemetry --cancellationPipeName /var/folders/g4/76q469c16sg48h2xcl17lm900000gn/T/vscode-tscancellation-d950e0e6639261af8c23.sock*
28515 /Users/wmertens/Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper.app/Contents/MacOS/Code Helper /Users/wmertens/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/typingsInstaller.js --globalTypingsCacheLocation /Users/wmertens/Library/Caches/typescript --enableTelemetry
90371 /Users/wmertens/Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper.app/Contents/MacOS/Code Helper /Users/wmertens/Applications/Visual Studio Code.app/Contents/Resources/app/out/bootstrap --type=extensionHost
90420 /Users/wmertens/Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper.app/Contents/MacOS/Code Helper /Users/wmertens/.vscode/extensions/dbaeumer.vscode-eslint-1.2.11/node_modules/vscode-languageclient/lib/utils/electronForkStart /Users/wmertens/.vscode/extensions/dbaeumer.vscode-eslint-1.2.11/server/server.js --node-ipc
The high CPU one was the bootstrap one, I killed it (regular kill signal) and that closed the other Helpers too. Using latest stable VSCode on macOS 10.12.4.
@wmertens Could you open a new issue (Help > Report Issues to get things pre-filled)? That must be a new problem, would be great if we could track that separately.
Version 1.15.1 have the same problem on Mac OS X 10.12.6. After quit vs code, there are still two Code Helper processes not killed.
I just had one now, I'm suspecting eslint or prettier. These were the
command line arguments:
PID TT STAT TIME COMMAND
86794 ?? R 13:12.32 /Users/wmertens/Applications/Visual Studio
Code.app/Contents/Frameworks/Code Helper.app/Contents/MacOS/Code Helper
/Users/wmertens/Applications/Visual Studio
Code.app/Contents/Resources/app/out/bootstrap --type=extensionHost
__CF_USER_TEXT_ENCODING=0x1F5:0x0:0x0
TMPDIR=/var/folders/g4/76q469c16sg48h2xcl17lm900000gn/T/
HOME=/Users/wmertens SHELL=/bin/bash
SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.6fiphXhfdk/Listeners
Apple_PubSub_Socket_Render=/private/tmp/com.apple.launchd.oS8bn6jW3r/Render
PATH=/Users/wmertens/.nix-profile/bin:/Users/wmertens/.nix-profile/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/usr/local/munki:/Users/wmertens/.nix-profile/bin:/Users/wmertens/.nix-profile/sbin:/Users/wmertens/bin:/Users/wmertens/bin/node_modules/.bin:/Users/wmertens/bin/node_modules/.bin:/Users/wmertens/bin
DISPLAY=/private/tmp/com.apple.launchd.6pEXQjW1HJ/org.macosforge.xquartz:0
LOGNAME=wmertens
XPC_SERVICE_NAME=com.apple.xpc.launchd.oneshot.0x10000017.Electron
COMMAND_MODE=unix2003
NIX_SSL_CERT_FILE=/Users/wmertens/.nix-profile/etc/ssl/certs/ca-bundle.crt
USER=wmertens XPC_FLAGS=0x0
NIX_PATH=nixpkgs=/Users/wmertens/.nix-defexpr/channels/nixpkgs:nixpkgs=/Users/wmertens/.nix-defexpr/channels/nixpkgs
GOOGLE_API_KEY=AIzaSyAQfxPJiounkhOjODEO5ZieffeBv6yft2Q LC_NUMERIC=C
VSCODE_NODE_CACHED_DATA_DIR_39496=/Users/wmertens/Library/Application
Support/Code/CachedData/8b95971d8cccd3afd86b35d4a0e098c189294ff2
VSCODE_NLS_CONFIG={"locale":"en-us","availableLanguages":{}}
VSCODE_PID=39496 VSCODE_IPC_HOOK=/Users/wmertens/Library/Application
Support/Code/1.15.0-main.sock CVS_RSH=ssh HOST=Wouts-MacBook-Pro.local
LC_COLLATE=en_US.UTF-8 PWD=/ SHLVL=1 TRAIL= L 39552.0811164405
_=/Users/wmertens/Applications/Visual Studio
Code.app/Contents/MacOS/Electron
AMD_ENTRYPOINT=vs/workbench/node/extensionHostProcess PIPE_LOGGING=true
VERBOSE_LOGGING=true VSCODE_WINDOW_ID=5
VSCODE_IPC_HOOK_EXTHOST=/var/folders/g4/76q469c16sg48h2xcl17lm900000gn/T/vscode-f54ba39c-67e2-4d48-a155-8458d996e1f6.sock
ELECTRON_NO_ASAR=1
CRASH_REPORTER_START_OPTIONS={"companyName":"Microsoft","productName":"VSCode","submitURL":"
https://rink.hockeyapp.net/api/2/apps/21a48a66799e47fea4f52c0ff81e803d/crashes/upload","extra":{"vscode_version":"1.15.0","vscode_commit":"8b95971d8cccd3afd86b35d4a0e098c189294ff2","vscode_sessionId":"b96d62b5-86ab-46b6-bec8-76c952c66e481503093992128","vscode_machineId":"c81d69dda26bfe0b2ad7279fadd0577679d0dcdefca885f47163e63f7e9dbfeb","processName":"extensionHost"},"crashesDirectory":"/var/folders/g4/76q469c16sg48h2xcl17lm900000gn/T"}
ELECTRON_RUN_AS_NODE=1 NODE_CHANNEL_FD=3
Interestingly, it went away when I killed it with the normal kill signal, I
didn't have to use -9.
Also note that this seems to be 1.15.0 and I'm now on 1.15.1; it must have
remained after the upgrade today.
On Sun, Aug 20, 2017 at 11:36 AM swingcoder notifications@github.com
wrote:
Version 1.15.1 have the same problem on Mac OS X 10.12.6. After quit vs
code, there are still two Code Helper processes not killed.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/27131#issuecomment-323574288,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADWlpBqdfi5sBFE4Vb6KJZIaePLhNu4ks5sZ_4LgaJpZM4NjjdN
.
some problem, have you find a way to fix this ?
Same here, please fix this, very annoying quit vscode and still Code Helpe consuming >100% CPU
Still happening for me sometimes.
I fixed this by killing all Code Helper's via terminal and then disabled Prettier - JavaScript formatter plugin.
After VS Code has restarted, it's not happening any more.
VS Code v. 1.17.2
Manually killing the problematic Code Helper process now pops up an error message on VS Code that an extension host has stopped. If I dismiss the notification without Restarting the Extension Host through the button, it does appear that Prettier stops working, so maybe that is the culprit.
EDIT: Sorry, I take that back, this problem has returned.
I have the version 1.17.2 and this problem has returned. I don't have any extensions installed and witout open any file the problem persists

The process responsible is this:
/Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper.app/Contents/MacOS/Code Helper /Applications/Visual Studio Code.app/Contents/Resources/app/out/bootstrap --type=watcherService
Most helpful comment
What I've noticed is that, even after closing VS Code, there are still some instances of Code Helper hanging around that are consuming upwards of 100+ % CPU.