To read all comments associated with this story, please click here.
Judging by the description, they do use seperate processes:
The b2g process may spawn a number of low-rights "content processes". These are where web applications and other web content are loaded. These process communicate with the main Gecko server process through IPDL, a message-passing system.
https://wiki.mozilla.org/B2G/Architecture
Basically, what Chrome does.
There are many reasons why Mozilla didn't change their architecture. The most important one is obviously compatibility with existing code. With B2G they didn't have that limitation.
Edited 2012-08-13 13:22 UTC
Oh, please. Why do you think nobody did it before Chrome? That solution is not better than the other: there are tradeoffs. One-process-per-tab is using a lot of ressources and makes it more difficult for add-ons to modify a webpage (e.g. Adblock in firefox blocks ads before they begin to download whereas Adblock in Chrome only hides/discharges them after they load).
Why do you want Firefox to look more like Chrome (which, alas, is the trend)? Use Chrome.





Member since:
2005-07-06
Given that they didn't even manage to rework Firefox's architecture to allow a process per website (a la Chrome), I would trust a Firefox OS as much as Windows95 i.e. not at all.