Linked by David Adams on Wed 3rd Aug 2011 16:50 UTC, submitted by _xmv
Thread beginning with comment 483641
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: Not a very good test
by _xmv on Thu 4th Aug 2011 18:05
in reply to "RE[3]: Not a very good test"
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.
actually its such statements that lead to incomprehension.
multiprocess is not technically the better solution but its the one that works best in practice, because it provides a higher isolation.
thats why chrome works well. its actually a pretty crappy browser in SOME regards. it crashes a lot, its quickly slowing down, etc
since its multiprocess it doesnt matter too much, everything is working properly again as soon as you close the tab
current firefox cannot do that. it cannot afford anything going wrong because resetting things back means restarting the complete browser




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