This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search 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.

Learn More

Cuireadh an snáithe seo sa chartlann. Cuir ceist nua má tá cabhair uait.

control process limit not showing

  • 1 freagra
  • 1 leis an bhfadhb seo
  • 12 views
  • Freagra is déanaí ó cor-el

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

All Replies (1)

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".