"Google Chrome Renderer?"

[jomama7366]

Has anyone else noticed that there is a process called "Google Chrome Renderer" which takes up 5-6 processes in Activity Monitor?



Initially, I was shocked and happy to see how little memory Chrome took up. But now, I'm not so sure. You add it all up, and it's about 350 MB or so!

Anyone else see this when they're running Chrome?

 

[mkrishnan]

I think that what you're seeing is the effect of the fact that Chrome uses a separate rendering engine for each tab or window you open. This was one of the major technological differences between Chrome and other browsers, at least at its launch.

 

[dukebound85]

I think that what you're seeing is the effect of the fact that Chrome uses a separate rendering engine for each tab or window you open. This was one of the major technological differences between Chrome and other browsers, at least at its launch.

Then what is google chrome helper? as I thought the helper was for each tab/window

 

[mkrishnan]

Then what is google chrome helper? as I thought the helper was for each tab/window

Hmmm, that is a good question... this blog post explains the process model in more detail, but it doesn't explain the worker/helper processes clearly.

 

[jomama7366]

I think that what you're seeing is the effect of the fact that Chrome uses a separate rendering engine for each tab or window you open.

Ahh, yes, that does explain it. Thank you so much.

 

[dukebound85]

Hmmm, that is a good question... this blog post explains the process model in more detail, but it doesn't explain the worker/helper processes clearly.

Interesting, it seems with the latest beta, the google chrome helpers have been renames to google chrome renderers from what i can tell

Here is another cool explanation comic style
http://www.google.com/googlebooks/chrome/small_00.html