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!

Om de ûnderfining foar jo te ferbetterjen is tydlik de funksjonaliteit dan dizze website troch ûnderhâldswurk beheind. Wannear in artikel jo probleem net oplost en jo in fraach stelle wolle, kin ús stipemienskip jo helpe yn @FirefoxSupport op Twitter en /r/firefox op Reddit.

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

FF is using only 4 of the 8 cores in my CPU. Why isn't it using all 8?

  • 5 antwurd
  • 3 hawwe dit probleem
  • 4 werjeftes
  • Lêste antwurd fan Burgomatic

more options

Task Manager shows that even when opening 15 pages in tabs, FF is still only using 4 out of the 8 cores in the CPU. Is FF made to utilize only 4-core CPUs?

Task Manager shows that even when opening 15 pages in tabs, FF is still only using 4 out of the 8 cores in the CPU. Is FF made to utilize only 4-core CPUs?

Alle antwurden (5)

more options

Firefox does not need to use 8 cores. 4 cores is plenty for it. Even games don't need 8 cores. Max, games would need is 4 cores.

Bewurke troch Microrobot op

more options

Firefox is 32 bit if you want to use all 8 cores you can use a 64 bit variant of firefox such as

NOTE: Both of these versions of firefox are unstable and may combust.

Bewurke troch kobe op

more options

Maybe because Firefox is a 32-bit application on a 64-bit operating system? Just a WAG.

more options

There is no need for Firefox to be using all your cores, that would just be a waste of resources and energy.

more options

I agree that there's no need to use all cores, but I thought modern apps were made to use all available power. I didn't know that this was caused by FF being a 32-bit app.

Thank you all for your answers.