With the next version of Firefox, Mozilla is planning to introduce a feature that should make the browser run much more smoothly, and it’s a move the company is calling the biggest change ever made to Firefox.
It’s called Electrolysis (E10S for short) and the feature, which has been in beta testing since December last year, effectively splits Firefox into a UI process and content process. With these two elements being separated, if a web page (the content process) happens to be eating up your CPU resources or crashing, the interface – all the various buttons and your other tabs which are open – will still remain responsive and fully usable.
That’s a pretty major boon to say the least, and will save a lot of frustration – there’s nothing worse than staring at your browser for 30 seconds solid with it being frozen and everything greyed out as some website churns away.
Stepping things up
Recently, the scale of beta testing Electrolysis has been stepped up, and over the last six weeks it has involved half of the testing population. And in terms of stability as well as the key issue of resource usage, things are apparently looking good.
Firefox 48 (with Electrolysis) will be unleashed to the general surfing population at the beginning of August, or at least that’s the plan, but there will be a staged rollout.
Mozilla’s Asa Dotzler wrote: “This is a huge change for Firefox, the largest we’ve ever shipped. But don’t worry. The Electrolysis team at Mozilla has a release roll-out plan that ensures we’re going slowly, measuring as we go and that we can throttle up as well as down depending on what we see.”
Apparently only 1% of users will receive Firefox 48 initially so Mozilla can test the waters and make sure everything is okay, before gradually rolling the release out to the rest of the user base.
Source: techradar.com
Nope!
Chrome (and IE) sandboxes tab processes for security reasons. Try and kill off a frozen Chrome process and you'll see it's likely to take the browser with it.
Chrome (or IE) doesn't separate the UI and content from each other.
This won't make people use Firefox more though.
So, something that Chrome has had for ages?
Chrome separates all individual processes ensuring that none that clashes affects the other. This processes include different tabs open, if you look into the Task Manager, you will actually see processes for your plugin, tabs open (name after page title) – Closing any process, does not affect the whole browser. Thats why a single page can freeze in chrome and not affect other pages unlike Firefox.
I am not sure i know what that exactly means, whats the difference between UI and Content, does not the content get rendered by the UI? Does that mean the browser will use more RAM? From my understanding, the content is un-rendered and has to occupy some RAM, then the rendered content has to occupy RAM also….someone dummy this one for me please