Firefox adopts multi-processes from Chrome, IE8

Chicago (IL) – Mozilla today confirmed a recent report from Mozilla Links that future Firefox versions will separate interface from content processes to increase the browser’s stability.

Process separation was first introduced by Google in Chrome was later adopted by Microsoft in Internet Explorer 8. Mozilla has trailed this trend, but has now confirmed that “future” Firefox browsers will also adopt process separation. Just don’t expect this feature to surface in the nearly finalized version 3.5.

As part of a new, unnamed project within Mozilla, a team is working to split the main (chrome) interface process from web content processes. The advantage of this approach is that a web page that may crash your browser today, will only crash a tab in the future, but the browser itself will stay alive. A simple demo of the feature is currently targeted for mid-July, but an actual implementation that previews split the interface and content processes is not expected until November.

Mozilla Links speculates that a publicly available split-process feature will not be available for another year. Sounds like Firefox 4, code-named Namoroka, to us.

Fore Firefox 3.5, Mozilla keeps stressing the performance improvements the browser will deliver. While most of the speed discussion surrounds the TraceMonkey Javascript engine, Mozilla has also highlighted performance enhancements to the bookmarks and history features as well as searches through the “Awesomebar”.