Platform Development • Re: e10s support question
As an aside, to demonstrate the issues with e10s, current release cycle Firefox security bugs that I just went through had 45 of the bugs I looked at directly related to e10s. In just this month. That's not counting issues that are less obviously prima facie caused by the e10s architecture of Firefox. Keep in mind how long ago this was introduced in Firefox, and we're still constantly having security issues in it every single month. It was supposed to be a "more secure" way of handling web content, remember? Because web content would be limited to its own less-trusted processes. Turns out it's suffering from exactly what I said, in that the messaging protocol itself is vulnerable to attack in ways a single-process browser would never have exposure to.
Discussion in the ATmosphere