Some have discovered a new project from the Mozilla Wiki documenting the first steps and timeline for Firefox to become a multi-process supporting browser. The project in question, simply known as Content Processes looks to separate processes to display the browser UI and web content.
Here are the current initial goals:
- Provide better application UI responsiveness
- Improve stability from slow rendering or crashes caused by content
- Improve performance, especially on multi-core machines
Now why do this, and what does it even mean? Well, both Google Chrome and Internet Explorer 8 have moved in this direction for increased stability. For an example, with multi-process support, a single tab crash wouldn’t take down your entire Firefox browsing experience. It would only effect that one tab, because it would be seen as its own process.
It might be a year or more before we see this in action via our own Firefox installations, however it is nice to see that Firefox is always looking to expand and check into other areas of stabilization to see if we can all benefit from it.