Well more to the point then, would that Chrome approach explain why I regularly have to force quit Chrome, even after doing a regular quit?
On Feb 8, 2012, at 9:47 AM, Arno Hautala wrote: > On Wed, Feb 8, 2012 at 09:37, list boy <[email protected]> wrote: >> >>> Chrome runs a separate task for each tab that is open. As well as a >>> process for the plugins. I'd guess that this is what you're seeing. >>> >>> Safari, by the way, does the same, but only uses one process for all >>> of the tab renderings and another for the UI. >>> >>> This way if a page hangs or crashes, the browser stays up and the >>> pages reload / re-render as necessary. >> >> For which, Chrome or Safari? > > For both. > > Try loading a few tabs in Safari and then kill "Safari Web Content" > using System Monitor.app. See what happens to your Safari tabs. > > With Chrome, you'll have to kill multiple processes named "Google > Chrome Renderer". > > -- > arno s hautala /-| [email protected] > > pgp b2c9d448
_______________________________________________ MacOSX-talk mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-talk
