Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

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.

Avatar for Username

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

This thread was archived. Please ask a new question if you need help.

content process limit

  • 2 பதிலளிப்புகள்
  • 4 இந்த பிரச்னைகள் உள்ளது
  • 54 views
  • Last reply by vj000000

primalbaily
primalbaily
more options

I have firefox nightly and the content process limit won't show up when I check or uncheck Hardware acceleration. how can I get to it and what is the name for the "content process limit" in the "about:config" section?

I have firefox nightly and the content process limit won't show up when I check or uncheck Hardware acceleration. how can I get to it and what is the name for the "content process limit" in the "about:config" section?

All Replies (2)

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

That is likely because in Nightly fission is enabled by default to make it possible to test for issues (fission.autostart = true). With fission enabled each tab has its own content process (i.e. all tabs are isolated), so you can't set a maximum and the Content Process settings are hidden.

See also:

  • about:config =>
    app.normandy.startupRolloutPrefs.fission.experiment.enrollmentStatus
    fission.experiment.enrollmentStatus (2:enable; 1:disable)

cor-el மூலமாக திருத்தப்பட்டது

vj000000
vj000000
more options

I recently noticed that the number of Firefox processes increased greatly. The number was over 19 and it was using up a lot of memory and, sometimes, a lot of CPU. I followed Cor-el's recommendation to turn off Fission and was able to set the process limit again. Thanks!