Funkcionalnosć tutoho sydła so přez wothladowanske dźěła wobmjezuje, kotrež maja waše dožiwjenje polěpšić. Jeli nastawk waš problem njerozrisuje a chceće prašenje stajić, wobroćće so na naše zhromodźenstwo pomocy, kotrež na to čaka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomhać.

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

content process limit

  • 2 wotmołwje
  • 4 maja tutón problem
  • 54 napohladow
  • Poslednja wotmołwa wot vj000000

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?

Wšě wotmołwy (2)

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)

Wot cor-el změnjeny

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!