According to Christopher Blizzard, Mozilla’s Web platform director, via a blog post, Mozilla has renewed its efforts to bring multiprocess browsing to Firefox. The post stresses the key advantages that process isolation will transfer to Firefox and tackles some of the requirements for Mozilla’s implementation.
Although multiprocess browsing became a higher priority for Mozilla after the release of Firefox 4, it is still not clear when the feature might land. Current and upcoming versions of Firefox do not yet have the feature, so chances that the it might hit the public by the end of this year are slim.
Blizzard continues to mention that moving tabs into separate processes can prevent certain kinds of crashes from taking down the entire browser, enable better hardware utilization on computers with multicore processors, improve the responsiveness of the browser’s user interface, and enable superior security sandboxing.
The way in which this architectural change will impact the Firefox memory footprint is a bit less transparent. Having processes for tabs will add to the memory overhead, but it also offers some benefits. Blizzard says that using different processes will reduce memory fragmentation problems and allow the browser better predict when to release memory when tabs are closed.
About (Author Profile)
Being passionate about software, Armin joined FavBrowser.com in early 2011 and has been actively writing ever since. Having accepted the challenge, he also enjoys watching anime, indulging in good books, staying fit and healthy, and trying new things.