News for hackers. Stuff that matters.
Re:Are They Slim Yet? Firefox, Chrome, IE, Safari by bitmapbrother on Friday March 10, 2017 @10:14PM (#13843999)
The test mentions he ran Firefox using 2, 4 and 8 content processes. Does this mean that Firefox does not use 1 process per tab like Chrome does?
Re:Are They Slim Yet? Firefox, Chrome, IE, Safari by fabrice_d on Friday March 10, 2017 @11:00PM (#13844139)
Firefox can be configured to use N number of content processes, and will allocate tabs among these processes. In FirefoxOS we were giving a new process to each tab/app, using a pre-allocated process to speed up startup (a version of that has been re-implemented for Firefox).

I'm not sure about the exact heuristics used by Chrome, but I think they do something like one process per origin.

Re:Are They Slim Yet? Firefox, Chrome, IE, Safari by bitmapbrother on Saturday March 11, 2017 @03:23AM (#13844780)
Yes, Chrome uses 1 process per domain. So I'm still not sure what would happen if Firefox is configured to use 4 content processes and 20 unique domain tabs are opened. Would the domains be distributed to these content processes? And what happens if 1 content process crashes? Would it also bring down all of the domains associated to it?
Re:Are They Slim Yet? Firefox, Chrome, IE, Safari by bzbarsky on Saturday March 18, 2017 @02:16AM (#13900165)
The answers to your questions are yes and yes.
Re:Are They Slim Yet? Firefox, Chrome, IE, Safari by saurik on Saturday March 11, 2017 @02:32AM (#13844658)
Chrome does not use one process per tab: open the Chrome task manager and you can see how it groups tabs by which process they are within.
Re:Are They Slim Yet? Firefox, Chrome, IE, Safari by bitmapbrother on Saturday March 11, 2017 @03:06AM (#13844735)
I opened up 16 unique top level domain URL's. Process explorer indicated that there were 21 processes of chrome.exe.

edit: as noted below it's one process per domain.

Re:Are They Slim Yet? Firefox, Chrome, IE, Safari by fulafel on Saturday March 11, 2017 @12:42AM (#13844416)
Chrome by default uses a process per domain, and shares that process with other tabs on the same domain. This is to align with security boundaries.
Re:Are They Slim Yet? Firefox, Chrome, IE, Safari by bitmapbrother on Saturday March 11, 2017 @03:13AM (#13844757)
Thanks for the clarification as I had always assumed it was one process per tab. Since it's one process per domain if one tab crashes does it also bring down the other tabs in the same domain?
Re:Are They Slim Yet? Firefox, Chrome, IE, Safari by fulafel on Saturday March 11, 2017 @10:54AM (#13845790)
Yep.
Re:Are They Slim Yet? Firefox, Chrome, IE, Safari by digi_owl on Saturday March 11, 2017 @12:47PM (#13846309)
Recent versions of Firefox have been pushing out pr tab process support (it has been called different things at different stages of development, i think the current label is e10s). There has been some controversy around this, as such support has in part been responsible for the removal of extensions in their traditional form.
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.