Ovo će web mjesto raditi na ograničen način, dok obavljamo održavanje stranice. Ako neki članak ne riješi tvoj problem i ako želiš postaviti pitanje, naša zajednica za podršku spremna je pomoći na Twitteru @FirefoxSupport i na Redditu /r/firefox.

Avatar for Username

Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

Ova tema je arhivirana. Postavi novo pitanje ako trebaš pomoć.

content process limit

  • 5 odgovora
  • 1 ima ovaj problem
  • 1 prikaz
  • Posljednji odgovor od hake

hake
hake
more options

I have a system with a 2 core processor, an Intel P4 3.2GHz. I cannot set a content process limit of 2 so I have to accept a single process incarnation of Firefox (60.4.0 ESR, 64bit). Is this intentional or is the minimum number of processor cores required to be at least 4.

I have a system with a 2 core processor, an Intel P4 3.2GHz. I cannot set a content process limit of 2 so I have to accept a single process incarnation of Firefox (60.4.0 ESR, 64bit). Is this intentional or is the minimum number of processor cores required to be at least 4.

Izabrano rješenje

This may be a stupid question, but you have multiprocess enabled right?

To check, do the following:

  1. Type about:config in the Firefox address bar
  2. Bypass the security warning
  3. Find browser.tabs.remote.autostart (there may be multiple)
  4. Set them all to true
  5. Restart Firefox.
Pročitaj ovaj odgovor u kontekstu 👍 1

Svi odgovori (5)

Wesley Branton
Wesley Branton
more options

You can set the content process limit to between 1 and 8. The default is 4, but you should be able to change this.

Go to the Firefox settings and go to the Performance section. Uncheck the Use recommended performance settings option and there you will find the content process limit setting.

If that content process limit setting appears locked, go to about:config in the Firefox address bar, bypass the warning and change the value of dom.ipc.processCount to anything between 1-8.

Hope this helps.

hake
hake Vlasnik pitanja
more options

Thank you Wesley. I am sorry to tell you that after changing dom.ipc.processCount to 2 in about:config, the content process limit remained grayed and unresponsive. although it did show the altered value of dom.ipc.processCount.

TaskManager still shows firefox.exe as a single process.

It wasn't long ago that Firefox 60 ESR ran with 4 processes regardless of the number of processor cores so something seems to have been changed in Firefox, it appears. Firefox will run 4 processes on a machine with a processor with 4 cores.

hake
hake Vlasnik pitanja
more options

I seem to have posted two replies so have erased the second of them.

Izmjenjeno od hake

Wesley Branton
Wesley Branton
more options

Odabrano rješenje

This may be a stupid question, but you have multiprocess enabled right?

To check, do the following:

  1. Type about:config in the Firefox address bar
  2. Bypass the security warning
  3. Find browser.tabs.remote.autostart (there may be multiple)
  4. Set them all to true
  5. Restart Firefox.
hake
hake Vlasnik pitanja
more options

The grayed out bits are now accessible. Back to where I thought I was. I don't remember making changes to those settings.

Anyhow, thank you very much Wesley. I would never have guessed that solution.