Firefox 48 e10s ativado, mas ainda um processo

Question

Eu habilitei e10s no Firefox 48. Eu verifiquei isso indo para about:support e vejo isso:

Multiprocess Windows     1/1 (Enabled by user)

Eu também desativei todos os complementos, mas quando abro guias de 4-5, consigo ver um único processo do Firefox.

Estou fazendo algo errado? Existe uma variável em about:config que limita o número de processos a 1?

Estou usando o windows 7.

    

Answer 1

A resposta aceita não responde à pergunta e está errada. O e10s pode ser ativado pelo usuário, que é o que o autor desta pergunta fez como indicado pelo about:support output.

Multiprocess Windows 1/1 (Enabled by user)

De acordo com o MozillaWiki

If you're using Firefox 48 or later, you might be using e10s already. Check about:support and look for a number higher than 0 in the "Multiprocess Windows" entry. If you would like to opt-in, open about:config and toggle browser.tabs.remote.autostart to true. On your next restart, e10s should be active.

Agora, voltemos à questão: O "Porquê" de Eletrólise

To ensure we don’t consume too much RAM, the first release of e10s will only use a single additional process for web content. We’ll add more processes in subsequent releases, as we become more memory efficient.

Então, para explicar, o Firefox não está usando um processo adicional para cada guia. O Firefox, no momento, está usando apenas um processo adicional para processar o conteúdo da web. Eventualmente, conforme os e10s evoluírem, eles serão divididos ainda mais.

    

Answer 2

Estou fazendo algo errado?

Não, você não está fazendo nada errado.

I've enabled e10s in Firefox 48.

A eletrólise não é ativada para todos os usuários do Firefox 48. No início, apenas 1% dos usuários terão e, posteriormente, até 50%.

Em particular, os usuários que estão usando extensões não terão a Eletrólise ativada.

Parece que, dependendo de quais extensões / extensões você está usando, você pode ter que esperar por uma versão do Firefox posterior a 50 (veja mais adiante nesta resposta para detalhes).

O que vem a seguir no Firefox com vários processos

This first phase of enabling our multi-process architecture is making its way to some of our Firefox 48 users starting this week. This is the biggest change we’ve ever made to Firefox, so we’re rolling it out slowly.

For Firefox 48, we’re only enabling it for classes of users that our testing shows it works well for and to begin with, we’ll only enable it for 1% of those users so we can check on the stability and engagement data and make sure nothing new and bad is showing up.

After that initial period, if all looks well, we’ll ramp up to 100% of those users, which will be about half of all Firefox 48 users.

Fonte O que vem a seguir para o Firefox com vários processos

Firefox 48 Beta, Release e E10S

When we hit release in about six weeks, not all of our Firefox 48 users will get E10S. The teams have been working really hard but we’ve still got some compatibility and other work to do to make E10S ready for everyone.

The groups that will have to wait a bit for E10S account for about half of our release users and include Windows XP users, users with screen readers, RTL users, and the largest group, extension users.

...

Complementos

If our Beta testing goes well, in Firefox 49 we will enable the multi-process architecture for users with a small set of add-ons that are known to work well with the multi-process architecture.

In Firefox 50, again provided beta testing goes well, we plan to enable the multi-process architecture for users with add-ons that have either set a flag to say they are compatible or that were built with our new WebExtensions add-on API which is compatible by design.

Eventually we will enable the multi-process architecture for all users and add-ons that are incompatible may no longer work. For this reason it is imperative that add-on authors update their add-ons to be compatible with the multi-process architecture.

Fonte Firefox 48 Beta, Release e E10S