[alistair75]

Short version: the Wired journalist doesn't really understand what they're talking about. I can't believe no-one has pointed this out yet.

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.

[vteven]

> In many cases, the plug-ins and processes they’re handling aren’t listed by name because the APIs don’t allow it. Google Chrome Helper is a martyr.

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.

[ahoge]

> 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.

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.

[Aldo_MX]

> That article is very badly written.

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.

[vdfs]

Thank you for saving our time!