Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Avatar for Username

Mozilla Destek’te Ara

Destek dolandırıcılığından kaçının. Mozilla sizden asla bir telefon numarasını aramanızı, mesaj göndermenizi veya kişisel bilgilerinizi paylaşmanızı istemez. Şüpheli durumları “Kötüye kullanım bildir” seçeneğini kullanarak bildirebilirsiniz.

Daha Fazlasını Öğren

Bu başlık arşivlendi. Yardıma ihtiyacınız varsa lütfen yeni bir soru sorun.

content process limit

  • 2 yanıt
  • 4 kişi bu sorunu yaşıyor
  • 2 gösterim
  • Son yanıtı yazan: 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?

Tüm Yanıtlar (2)

cor-el
cor-el
  • Top 25 Contributor
  • Moderator
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 tarafından tarihinde düzenlendi

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!