Chrome Helper Using Too Much CPU
Reported by
boryago...@gmail.com,
Dec 10 2016
|
|||||
Issue description
How can I fix this? I really don't want to use another browser. No threads online were able to provide me an adequate solution to remediate. Thanks
<b>Chrome Version : <Copy from: 'about:version'></b>
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
Safari:
Firefox:
IE:
What steps will reproduce the problem?
(1)
(2)
(3)
What is the expected result?
What happens instead?
Please provide any additional information below. Attach a screenshot if
possible.
,
Dec 12 2016
Mac Os Sierra 10.12.1 Chrome version Version 54.0.2840.98 (64-bit) Regards, Boris Godin
,
Dec 14 2016
What websites are you visiting when you encounter this issue? Do you have any extensions installed, and if so, which ones? Also, please submit a trace of the bad behavior using these instructions: https://www.chromium.org/developers/how-tos/submitting-a-performance-bug Thanks.
,
Dec 15 2016
It's not a website issue. These Google Chrome Helpers are always running in the background. It takes up roughly 5-6GB of my Ram, while idle. Regards, Boris Godin
,
Dec 15 2016
Is the concern about CPU usage, memory, or both? If it's about CPU, it would be helpful to still take a trace when CPU is high and as few tabs as possible are open (ideally only one).
,
Dec 15 2016
Memory is the primary area of concern. CPU isn't over worked. How do I remove those google helper add ons
,
Jan 20 2017
@rschoen-- Could you please respond to comment #6 and update the thread accordingly. Thanks in advance!
,
Jan 23 2017
,
Jan 23 2017
Can I speak with someone over the phone? Regards, Boris
,
Jan 25 2017
Hi boryagodin, If you're looking for ways to reduce memory usage, you may find this article helpful: https://support.google.com/chrome/answer/6152583?hl=en Unfortunately bugs.chromium.org is a place to submit technical bugs with Chrome, and not a support forum. I understand you are not happy with the amount of memory Chrome is using, but without sending us more information about how the bad behavior is triggered or a memory dump from Chrome itself there is unfortunately very little we can do to resolve the issue. I'm going to mark the bug as WontFix, but please feel free to provide more actionable information for us if you'd like, and we can reopen the bug. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ajha@chromium.org
, Dec 12 2016