Este site irá ter funcionalidade limitada enquanto fazemos manutenção para melhorar a sua experiência. Se um artigo não resolve o seu problema e quiser colocar uma questão, temos a nossa comunidade de apoio à espera de o ajudar em @FirefoxSupport no Twitter, /r/firefox no Reddit.

Avatar for Username

Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais

Esta discussão foi arquivada. Se precisar de ajuda, por favor, coloque uma nova questão.

control process limit not showing

  • 1 resposta
  • 1 tem este problema
  • 12 visualizações
  • Última resposta por cor-el

fransiskus.nugraha
fransiskus.nugraha
more options

Hi,

My firefox has been consuming lots of memory (and many CPU processes) for quite some time now.

I read that i can adjust the number of multiple content process, but somehow i am not seeing it inside about:preferences menu even after i checked 'Use hardware acceleration when available' option.

Do advise me on what should i do to improve my firefox speed?


Regards,

Frans

Hi, My firefox has been consuming lots of memory (and many CPU processes) for quite some time now. I read that i can adjust the number of multiple content process, but somehow i am not seeing it inside about:preferences menu even after i checked 'Use hardware acceleration when available' option. Do advise me on what should i do to improve my firefox speed? Regards, Frans

Todas as respostas (1)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

There has been a slow rollout of Fission (Site Isolation) in Firefox, so if you notice you have more content processes than in the past then you might have been selected to participate in this experiment and have Fission enabled. Fission is about a new site isolation architecture in Firefox and you will see more Firefox processes running than before and when Fission is enabled you can no longer limit the number of content processes in Settings or via dom.ipc.processCount on the about:config page. You can check the current Fission state on the "Help -> More Troubleshooting Information" (about:support) page (search for Fission).

You can set fission.autostart = false on the about:config page to opt-out of this experiment and disable Fission.

You can open the about:config page via the location/address bar. You can click the button to "Accept the Risk and Continue".