There is a Google Chrome Helper process for each tab you have open, for each extension you have installed, for each plugin that is currently running and one to talk to the GPU in your system.
If you enable "Click to play" and open Chrome with one empty tab you'll still have at least two Google Chrome Helper processes. One for the empty tab and one for the GPU process. If you've installed any extensions you'll have more. There is no way to "destroy the Google Chrome Helper".
That article is very badly written.
The author's chief complaint is that Google Chrome Helper obscures the source of crashes/hangs, making diagnosis that much harder. The article is badly written, sure; but the workaround does allows you to isolate suspect content from everything else.
You can see the CPU/RAM/network utilization of each in Chrome's task manager. You can open it via Shift + Esc or ☰ -> More Tools -> Task Manager.
I would not claim this, I would take the article as an example of what the average user thinks it's happening in their computer, and I would use the article as a reference to make things clearer to the users in the future.
Interestingly the solution to problems with it is the same as implemented in Opera 12 years ago: Configure the browser to run plugins only when the user explicitly activates them.
I'd recommend it if anyone else has noticed a slow down at all.
And yes, I know, it has all the terrible ShellShock bugs and other stuff that will never be fixed, but I just need to run some OS X software time from time and I won't buy a new Mac because of that.
And when I tried to install Linux on that, Wi-fi didn't work properly, and there were some other issues I had with I think rebooting and maybe some other hardware stuff (I know, it sounds like a cliche, but it's true)
Filtering out HTML5 video ads is harder (though if you block everything set to auto play you do OK).
How do i do this on chrome?
I seems brain damaged to me to do it via a browser extension since I use multiple browsers, not to mention other programs that make http/https/ftp connections (e.g. RSS reader, mail reader etc).
to_clipboard = (text) ->
textarea = document.getElementById "copy-workaround"
textarea.value = text
document.execCommand "copy", false, null
Chrome for Mac is almost useless because of this issue. I first encountered this just after Maverics release and Google has not fixed it until now. Very odd.
Issue 373923 - chromium - Google Chrome Helper Process Taking up >100% CPU on Macs
Issue 397642 - chromium - Google Chrome Helper (not responding) on Yosemite Beta 1
Issue 399960 - chromium - Video playback, CSS transitions, and other GPU operations drastically heat up 13" Retina Macbook Pros
Issue 367593 - chromium - Multiple Google Chrome Helpers are spawning and slowing severely slowing down my browser
Google Chrome Helper using far too much CPU power - Google Group
I end up just leaving two browsers with different profiles loaded half the time, one of them tweaked to be as revealing as possible, for loading stuff I just want to see and don't want to play unblocking games with. Then when I close it all the cookies, localstorage, etc. goes poof. As he said, it's almost fun. Not actually fun.
The thing is, there's no flash involved. We've narrowed it down to css3 transitions running amok. In other cases we've poorly constructed JS loops causing problems.
Recently i've noticed it on everything (even gmail, drive and calendar) in chrome.
No problems elsewhere, although in a side-by-side comparison with mozilla showed mozilla nearing similar cpu usage (30-60%) but never sustained (lasting seconds)
Not sure if this helps anyone, or if this is just 'duh.' The css3 transitions being involved i have not read out in the wild, so i thought i'd toss that idea out.
I know this isn't the same issue just a whole bunch of annoying things about chrome
For example, it allows one to see CPU & Mem usage per tab. It also has the ability to kill problematic tabs, extensions and background processes with ease.
Chrome's Task Manager can be found under Menu Icon -> (More) Tools.
In fact, this feature was being used often enough, that I ended up assigning it a shortcut. (for me: command-shift-1)
You can kill groups of tabs that are part of the same process. BUT that does not mean that you can kill individual tabs via the Task Manager and the main source of my complaint.
I don't care if I don't have flash (actually I care to NOT have flash). So what reason would there be to not simply run Chromium? Or am I forgetting something useful that I'm likely using?
They’re using DASH with small .mp4 snippets. It’s also the reason why videos don’t load completely anymore and why audio and video sometimes go out of sync. Also the reason why nothing works as expected.
In theory, this is what memory paging is for. In practice, this is higher level and seems to work much better.
Anyone else seen or worked-around this? (It's been a while since it's noticeably recurred, so maybe it's been fixed.)
Don't do that.
No seriously, don't do that.
These kinds of apps do nothing but prey upon the gullible. They're worse than useless; they actually decrease the performance of your system.
The OS is actually remarkably good at managing memory. Like, staggeringly good. Especially in Yosemite. Beyond that, the OS actually wants to keep as little RAM "free" as possible. "Free" RAM is wasted RAM. It uses that RAM to store memory that might be used again in the future. That's what "Inactive" is; it's memory that is not currently being used, but contains stuff that may be used again, and if it's not, that stuff can be thrown out in order to provide the memory to another application.
And yet, the application you linked says that its primary purpose is to "purge" this inactive memory. That's counterproductive. If another app needs it, the memory will be given to that app whether or not it's been "purged". The only thing that "purging" it does is remove the ability to reuse the original contents of the memory.
I'm guessing this is why Activity Monitor in Yosemite doesn't even list "Inactive" memory anymore (or "Free"). Instead it has "File Cache". On my iMac right now, with 20GB of RAM, the "File Cache" is "11.02GB". And that's fine. That's great. It means if any of the cached file data is needed, it's already in memory. That's vastly better than leaving it around as "free" memory.
Every modern OS behaves this way. It's deliberate, it's absolutely crucial for good behavior, and "memory clean" apps do nothing but hurt the performance of your system.
So don't use it.
I think this panic started with Windows Vista where there was no distinction between actually used memory and memory used for caches and buffers. Hence the complaints about how Vista was so inefficient, it didn't have enough memory even when freshly launched with no apps open.
Any anecdotal data on that?
Either way, the weird thing is that if you go to the Window menu and hit Task Manager... you can monitor extension CPU usage, etc.
I never had a problem until recently, and yet now I'm seeing red in the Activity Manager due to Chrome. It's bizarre.
I only use Chrome if I need to use a site with Flash and I use the "Open Page With" item in Safari's Develop menu to open the appropriate page. Then, I quit once I'm done with it.