Re:Firefox 48 Beta, Release, and E10S
by piotrjurkiewicz on Tuesday June 07, 2016 @08:05AM
(#11853844)
> The goal must be [...] multiple content processes for each tab
According to the wiki page you linked, it doesn't seem to be the goal for them:
"The (practically) unlimited process count is on some platforms not a realistic goal, and having a separate process for each open site instances or even sites does not seem like a reachable goal (for now at least). Which means using content processes as a security membrane cannot be a goal either."
If this is true, I don't see any advantages of e10s introduction.
Re:Firefox 48 Beta, Release, and E10S
by deprave on Tuesday June 07, 2016 @09:29AM
(#11854340)
They're going to find out that managing processes by themselves is going to be very difficult (similar to M:N threading), and opt for a Chrome-like model where each tab is its own process.
According to the wiki page you linked, it doesn't seem to be the goal for them:
"The (practically) unlimited process count is on some platforms not a realistic goal, and having a separate process for each open site instances or even sites does not seem like a reachable goal (for now at least). Which means using content processes as a security membrane cannot be a goal either."
If this is true, I don't see any advantages of e10s introduction.