Re: Chrome yet?
On Wed, Feb 8, 2012 at 14:22, list boy wrote: > 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? Maybe, though I can't say that I see this sort of behavior. -- arno s hautala /-| a...@alum.wpi.edu pgp b2c9d448 ___ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk
Re: Chrome yet?
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 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/-| a...@alum.wpi.edu > > pgp b2c9d448 ___ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk
Re: Chrome yet?
On Wed, Feb 8, 2012 at 09:37, list boy 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 /-| a...@alum.wpi.edu pgp b2c9d448 ___ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk
Re: Chrome yet?
>> Anyone know the deal with Chrome? >> I'm up-to-date (v17.0.963.46) w Lion (10.7.2) >> and I keep getting these weird multiple listings of it in my open processes >> list (iStat Menus) > > 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?___ MacOSX-talk mailing list MacOSX-talk@omnigroup.com http://www.omnigroup.com/mailman/listinfo/macosx-talk
