Linked by David Adams on Wed 3rd Aug 2011 16:50 UTC, submitted by _xmv
Permalink for comment 483641
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
More Features »
Sponsored Links



Member since:
2006-01-02
Oh really? So explain to me: how do you know which tab use 99% of CPU/too much memory in Firefox?
With Chrome it's easy: it has an integrated "task" manager. "
In Nightly (Firefox 8), in about:memory you can see how much memory each tab uses. In general it's true that multiple processes make it easier for the user to know which tab is using what.
Firefox is eventually moving to a multi-process architecture a la Chrome (though that's probably still 6 months away). So for sure Mozilla agrees that's the better approach. But notice that not even Chrome can rely on that for security, since above a certain number of open tabs, multiple tabs end up sharing the same process. I also wouldn't say that "threads are an optimization, that's all". Threads are light-weight processes, i.e. processes that share the same address space.
Edited 2011-08-04 13:48 UTC