Avatar for Username

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Learn More

Dieses Thema wurde archiviert. Bitte stellen Sie eine neue Frage, wenn Sie Hilfe benötigen.

control process limit not showing

  • 1 Antwort
  • 1 hat dieses Problem
  • 14 Aufrufe
  • Letzte Antwort von 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

Alle Antworten (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".