News for hackers. Stuff that matters.
Re:Are They Slim Yet? Firefox, Chrome, IE, Safari by bogas04 on Friday March 10, 2017 @11:01PM (#13844143)
It does not. They are experimenting with different models and will probably use 4 processes for all tabs.
Re:Are They Slim Yet? Firefox, Chrome, IE, Safari by throwaway91111 on Saturday March 11, 2017 @12:30AM (#13844384)
I was under the impression the primary benefits of the process design were containing failure and jailing vulnerabilities to avoid them from accessing your other tabs. Why not do one process per iframe/origin?
Re:Are They Slim Yet? Firefox, Chrome, IE, Safari by arantius on Monday March 13, 2017 @09:20AM (#13857539)
AIUI It's about separating all untrusted web content from everything else on your computer. As long as you have _one_ content process (and one parent/browser process), you get the vast majority of security benefits (by limiting the capabilities of that child content process).

The same origin policy already works fine, when talking content-to-content.

Re:Are They Slim Yet? Firefox, Chrome, IE, Safari by azakai on Saturday March 11, 2017 @01:11AM (#13844484)
More processes do have benefits, but they increase memory usage, as measured in that link.