News for hackers. Stuff that matters.
Re:Chrome 55 uses 30% less memory than 54 by fulafel on Sunday December 04, 2016 @01:05AM (#13098973)
The primary security gain of sandboxing is about making it harder for web content to hijack your computer by exploiting security bugs. Many common types of bugs can be exploited to get remote code execution in browsers because of unsafe programming languages used (C/C++).

Both Chrome and Firefox have multi-process sandboxes now, Firefox is a little behind and plans to enable multiple content processes next year.

While Chrome's is more granular, it does share processes between web pages from the same domain so won't start a new one for quite every tab.

Re:Chrome 55 uses 30% less memory than 54 by strcat on Tuesday December 06, 2016 @10:41PM (#13120296)
They're shared among site instances, not the same domain. It has to do with web standard semantics. Google has been working on https://www.chromium.org/developers/design-documents/site-is... for quite some time which will probably ship in 2017. That's the next step beyond the --process-per-site-instance after --isolate-extensions.

Firefox is more than just a little bit behind when it comes to sandboxing though... there's a LOT more to sandboxing than splitting up processes. That doesn't result in any meaningful isolation without a lot of further work, and improving sandboxing is a major undertaking that Chrome has been working on for years.