Dette websted vil have begrænset funktionalitet, mens vi gennemgår vedligeholdelse for at forbedre din oplevelse. Hvis en artikel ikke løser dit problem, og du vil stille et spørgsmål, har vi vores supportfællesskab, der venter på at hjælpe dig på @FirefoxSupport på Twitter og/r/firefox på Reddit.

Avatar for Username

Søg i Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Læs mere

Denne tråd blev arkiveret. Stil et nyt spørgsmål, hvis du har brug for hjælp.

control process limit not showing

  • 1 svar
  • 1 har dette problem
  • 12 visninger
  • Seneste svar af 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 svar (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".