Posted by jpluimers on 2016/01/29
I’m not the only one with a Mac having issues with Google Chrome Helper CPU usage, but most of the entries are for older Chrome versions. So below are the steps I performed. There are also pros and cons are after the steps.
In chrome://settings/content, under “Plugins”, I ticked “Let me choose when to run plugin content” (it was at “Detect and run important plugin content (recommended)”. That dialog doesn’t allow you to copy it’s content, so no HTML, just this screenshot:
In chrome://plugins/ I disabled this one:
Adobe Flash Player – Version: 20.0.0.267 (Disabled)
Shockwave Flash 20.0 r0
| Description: |
Shockwave Flash 20.0 r0 |
| Location: |
/Users/jeroenp/Library/Application Support/Google/Chrome/PepperFlash/20.0.0.267/PepperFlashPlayer.plugin |
| Type: |
PPAPI (out-of-process) |
| MIME types: |
| application/x-shockwave-flash |
Shockwave Flash |
|
| application/futuresplash |
Shockwave Flash |
|
|
|
Pros of these settings:
- If you have a lot of tabs open (many of them suspended using The Great Suspender), then Google Chrome Helper uses far less CPU.
- Youtube doesn’t use the Flash Player any more. It now uses HTML5 which seems far more battery friendly and more responsive.
Cons of these settings:
- PDFs don’t automatically open any more, nor auto-download. You get something like this:
.
–jeroen
Posted in Apple, Chrome, Google, Mac, MacBook, MacBook Retina, PDF, Power User | Leave a Comment »
The Wiert Corner - irregular stream of stuff 