Code helper renderer mac os что это

Code Helper high CPU usage on Mac #59656

Comments

andreixk commented Sep 28, 2018

Issue Type: Performance Issue

After a few hours the VS Code module (Code Helper) started using over 100% CPU. The problem persists even after exiting VS Code.
The issue posted by another user is closed for some reason, but the problem has not been addressed in any way.

VS Code version: Code 1.27.2 (f46c4c4, 2018-09-12T07:04:11.329Z)
OS version: Darwin x64 17.4.0

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz (8 x 2500)
GPU Status	2d_canvas: enabled checker_imaging: disabled_off flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on native_gpu_memory_buffers: enabled rasterization: enabled video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled
Load (avg)	2, 2, 2
Memory (System)	16.00GB (0.80GB free)
Process Argv	/Applications/Visual Studio Code.app/Contents/MacOS/Electron
Screen Reader	no
VM	0%

Process Info

Extensions (21)

Extension	Author (truncated)	Version
insertnumbers	Asu	0.9.1
npm-intellisense	chr	1.3.0
bracket-pair-colorizer	Coe	1.0.60
vue-peek	dar	1.0.2
vscode-eslint	dba	1.6.0
gitlens	eam	8.5.6
vscode-npm-script	eg2	0.3.5
json-tools	eri	1.0.2
prettier-vscode	esb	1.6.1
auto-close-tag	for	0.5.6
auto-rename-tag	for	0.0.15
diff-tool	jin	0.0.1
prettify-json	moh	0.0.3
vscode-attrs-sorter	mrm	2.1.0
vetur	oct	0.12.7
vscode-icons	rob	7.27.0
vuejspack	she	1.3.2
vscode-fileutils	sle	2.11.0
vscode-todo-highlight	way	1.0.4
vscode-import-cost	wix	2.9.0
JavaScriptSnippets	xab	1.7.0

The text was updated successfully, but these errors were encountered:

Источник

Mac: Code Helper (Renderer) wants to use your confidential information #1759

Comments

foucdeg commented Dec 17, 2019

Since recently, when I open VS Code with my usual extensions, I get a system password prompt with the following message:

Code Helper (Renderer) wants to use your confidential information stored in «VS Code Azure» in Keychain.

This thread microsoft/vscode#84932 (comment) had me disable my extensions one by one until I was able to single out the Azure Functions extension. When it is disabled, the behaviour doesn’t happen. This is new behaviour (I’ve used the extensions since June and the issue happened two weeks ago).

How can I avoid this password prompt?

The text was updated successfully, but these errors were encountered:

ejizba commented Dec 20, 2019

The Azure Account extension uses keychain on Mac to store login information, which is probably why you’re getting prompted. Are you signed in to Azure? Did you update your OS a few weeks ago? I feel like I’ve heard the lastest Mac OS might’ve changed something. To fix the root cause, you’d probably need to file an issue on the account extension directly: https://github.com/microsoft/vscode-azure-account

From the Functions extension, we might be able to mitigate the issue by delaying our request to get account info until absolutely necessary (resulting in fewer prompts). Would need further investigation.

foucdeg commented Dec 24, 2019

Thanks @EricJizbaMSFT , I did update MacOS recently. Will file an issue on the other repo.

Источник

VS Code — Code Helper process using more than 100% CPU on macOS

I noticed that my MacBook gets hot and noisy (fans) when using VS Code (v1.31). The Activity Monitor shows the process Code Helper using more than 100% of CPU. It started happening with one repository which is huge. Only one window opened, no files opened, and it always uses more than 100% CPU.

Checking in Microsoft/GitHub, there was an issue reported but they closed it saying «This issue has been closed automatically because it needs more information and has not had recent activity.» , but it is still an ongoing issue. I tried some of the recommendations in the comments but didn’t work.

Does anybody has more info and/or know how to avoid this? Is it possible to make some configurations for VS Code to not burn the MacBook?

4 Answers 4

The behaviour you describe could either be a bug in VS Code or it is intended behaviour simply because the numbers of files you have require large amounts of CPU time to process. I strongly suspect that the problem is a bug.

The issue you have found have the same externally observables as your problem, i.e. the CPU usage of Code Helper is very high. However there could be many different reasons for that to happen. Therefore it is not a problem that that specific issue has been closed for outside comments.

I would highly suggest opening a new issue instead. Go to this page:

And click the «New issue» button. Select that you want to file a «Bug report». Then please describe everything carefully, including which of the recommendations you have tried that did not work.

Hopefully the VSCode team will be able to fix the bug and release a new and fixed version.

Источник

Code helper : High CPU usage on macOS Sierra #31388

Comments

sanghin commented Jul 25, 2017

VSCode Version: 1.14.2 OS Version: macOS Sierra Version 10.12.5

Steps to Reproduce:

Reproduces without extensions: Yes

ps aux | grep -i code

The text was updated successfully, but these errors were encountered:

jkwuc89 commented Aug 2, 2017 •

I am seeing this as well inside VS Code 1.14.2. To make matters worse, the Code Helper process is left running when I quit VS Code. Fortunately, a reboot is not necessary. Fire up Activity Monitor and force quit the Code Helper process.

jkwuc89 commented Aug 4, 2017

Here are some simple reproduction steps for this issue:

1. Open a terminal and change to your $HOME directory
2. Run code —disable-extensions .
3. Open Activity Monitor. Observe that the Code Helper process is running at well over 100% CPU usage. My guess is that this is caused by it parsing through the entire $HOME directory tree structure.
4. Quit code by pressing Cmd + Q. Inside Activity Monitor, observe that Code Helper is still running and its CPU usage is still over 100%. It does eventually go away.

bpasero commented Aug 11, 2017

The original authors process that is 100% seems to be TypeScript: damien 29107 100,0 3,1 3428428 261784 ?? R 3:45 8:39.02 /Applications/Visual Studio Code.app/Contents/Frameworks/Code Helper.app/Contents/MacOS/Code Helper /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/node_modules/typescript/lib/typingsInstaller.js —globalTypingsCacheLocation /Users/damien/Library/Caches/typescript/2.4 —enableTelemetry

arxpoetica commented Sep 13, 2017

Following @jkwuc89’s steps, I can confirm that it’s freaking out, specifically in the $HOME directory:

wind2412 commented Oct 4, 2017

I have the same problem. Vscode version is the newest 1.16.1 now. However the CPU level is so high and my mac got very hot. Although I quitted vscode, the two code helper processes are working background so that I must kill them by myself. I’m writing c++.

darkdescendant commented Oct 7, 2017

Ditto with VSCode 1.7X I just updated today. Even after quitting VSCode Code helper and it’s python processes absorbed all the memory on my machine (disk and RAM). The only time I’ve ever seen Mac OS X complain about system put of memory is the 2 times I’ve tried to use VSCode at work. Not sure what is going on but obviously there is some sort of run away processing going on with codehelper.

The code base I am using this on is a large C++ and C# code base.

xiaoshuw commented Oct 8, 2017

I have the same problem with 1.17. What is strange is it only occurs to one project directory. Don’t know why is that as other directory used to develop vue component seems all right. I have tried to set useExperimentalWater and add file.excludes etc. It is the same result.

wind2412 commented Oct 8, 2017

@darkdescendant After I banned the Microsoft C++ extensions, my cpu level seems to be normal again. My Activity Monitor tells me the Microsoft C++ extensions make cpu in a high level. However, C++ extensions got updated yesterday and I didn’t make a test. @xiaoshuw Vue I don’t know.

darkdescendant commented Oct 8, 2017

Yeah, I figured it was that extension. But since that is the whole reason for me in using VSCode over Sublime it kind of kills it for me. 🙁

I might re-install and see what happens since you noted the extension was updated.

darkdescendant commented Oct 8, 2017

xiaoshuw commented Oct 8, 2017

Well, mine doesn’t have the C/C++ extension. Also, it doesn’t have issues in one project but does have on another. As I am using the vscodevim, it renders the vscode useless because after one key stroke, it seems waiting for the run-away process so it effectively useless. I didn’t have problem with 1.16, it only started after recent update.

markeissler commented Oct 27, 2017

High CPU on macOS is the number one thing that drives me nuts on VSCode and the very next thing is the fact that it’s such a pain to debug. MS really needs to provide some tools outside of the standard Google Dev Tools (which don’t make it easy).

What I want to see is that VSCode monitors resource usage and runaway extensions. I want to see a pop up or some other easy-to-read diagnostic along with an offer to disable the offending extension. The last thing I want to do is to spend so much time debugging my development tools themselves.

mjbvz commented Oct 27, 2017

@sanghin Do you still see the originally reported TypeScript cpu issue on VSCode 1.18 insiders? If so, does this reproduce for all folders you open or just some of them?

For anyone seeing high cpu usage with the C++ extension, please try following up with that extension instead

xiaoshuw commented Oct 28, 2017

I can no longer see the run away process anymore — with the same 1.17. I didn’t do anything — besides in between I have probably rebooted my machine a few times. I didn’t use TypeScript. As I said earlier, I have two projects of similar setup. Only one project had this issue.

wind2412 commented Oct 28, 2017

In fact, I think the C/C++ Extension gets much better after updating its version. These days there is only one time getting very hot but soon it gets normal cpu level.

sanghin commented Oct 30, 2017

@mjbvz Sorry for my late (late) response. This issue can be closed. I’m now on :

• VSCode 1.17.2 (1.17.2)
• High Sierra Version 10.13

Источник

Code Helper (Renderer) uses 100% of CPU in background but nothing is open #101555

Comments

esprehn commented Jul 2, 2020

VSCode Version: May 2020 (version 1.46) OS Version: OS X 10.15.5 (19F101)

Steps to Reproduce:

1. Use VSCode for a while
2. 100% CPU usage even though no tabs are open.

Strangely the process explorer for VSCode doesn’t show the process, but Activity Monitor shows it owned by the extensionHost. It seems like VSCode doesn’t know about this process anymore even though it belongs to it and is using 100% of the CPU.

Does this issue occur when all extensions are disabled?: Yes/No

The text was updated successfully, but these errors were encountered:

esprehn commented Jul 2, 2020

Note in the above attached screenshot that the process using 100% of the CPU is not in the VSCode Process Explorer, but has the pid of the extensionHost as the parent.

Here’s a sample from Activity Monitor that shows it’s running a lot of JS in that process.

JacksonKearl commented Jul 2, 2020

vscode-triage-bot commented Jul 2, 2020

Thanks for creating this issue! We figured it’s missing some basic information or in some other way doesn’t follow our issue reporting guidelines. Please take the time to review these and update the issue.

esprehn commented Jul 7, 2020 •

@JacksonKearl per my bug report whatever extension this is doesn’t show up in any of the tools because it’s not connected anymore. I did attach a profile, but the Process Explorer and other tools don’t show the runaway process.

fortinmike commented Jul 30, 2020 •

I also see this bug. Same repro steps. I did not notice this being an issue until recently.

macOS Catalina 10.15.6 (19G73)
VS Code 1.47.3

I can add that the processes stay alive and at 100% CPU even after VS Code is quit completely:

In the above screenshot, I have only one stray process running, but just this morning I had the exact same issue, but with two processes taking 100% CPU each. Killing the processes manually fixes the issue for a few hours at most.

Like @esprehn I don’t see the processes in VS Code’s Process Explorer.

JacksonKearl commented Jul 30, 2020

@deepak1556 maybe you can make some sense of these cpu profiles?

deepak1556 commented Jul 31, 2020 •

@esprehn thanks for the process sample, I have not been successful analyzing the sample trace. Here is the dsym download link https://electron.blob.core.windows.net/builds/7.3.1/vscode/4994287/electron-v7.3.1-darwin-x64-dsym.zip incase you would like to try.

If the issue still continues to happen with latest insiders https://code.visualstudio.com/insiders/, can you re-record the trace using Instruments.app > Time Profiler , choose the offending process to trace

Load the symbols from File menu > Symbols , here are the download links

With symbols loaded, save and attach the trace here.

@fortinmike please do the same, thanks!

webOS101 commented Aug 3, 2020

I also see a lot of these proesses. Here’s a sample of some interesting ones:

VS Code is not running. I often see the Code Helper process taking up 100% or more of CPUs and shutting down VS Code usually cleans that up. It’s not really helpful that have to do it, but I discovered today that there are a lot of lingering processes even after shutting down VS Code

deepak1556 commented Aug 3, 2020

@webOS101 those processes are not from the core, some extension is spawning child process to do a node script evaluation node -e var p = process;p.on(‘message’,function(m)else if(m.c===’rs’));>catch(err));>>>); using the helper executable. Does you see the process when you run with —disable-extensions ? can you try narrowing down the faulty extension ?

fortinmike commented Aug 9, 2020 •

Maybe figuring out which extensions we have in common might be a good start to find out which one causes this? Here are mine, minus themes (as listed in

webOS101 commented Aug 10, 2020 •

I missed the response earlier! My list is quite a bit smaller:

webOS101 commented Aug 10, 2020

I did a grep for the offending string and, per my expectation, found it in the eslint plugin:

dbaeumer commented Aug 17, 2020

That process should only have a very short life. It is used to resolve the eslint node module. @webOS101 can you reproduce this?

webOS101 commented Aug 17, 2020

I can’t reproduce the lost processes at will. I’m not sure what triggers it. The pegged CPU while VS Code is open is easy to reproduce. I suspect, maybe, after the process gets pegged, it might be possible to trigger the other somehow but I haven’t figured out reproduction steps.

Sixthdim commented Sep 8, 2020

I too am having this issue several times per day. Here is my bug report paste:

Hi! I have been running into this issue several times a day on my Mac where the «Code Helper (Renderer)» process gets stuck using 100% CPU and my fans go into jet engine mode. This usually happens when I switch between Git branches. When this does happen, I lose the ability to «Go to Definition» or «Peek» within my code. To fix the issue, I need to quit VS Code and force quit the helper process from Inspector. The code I’m working in is mostly TypeScript. Thanks!

VS Code version: Code 1.48.2 (a047975, 2020-08-25T10:09:08.021Z)
OS version: Darwin x64 19.6.0

Источник