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ć.

Avatar for Username

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

Tuta nitka je so archiwowała. Prošu stajće nowe prašenje, jeli pomoc trjebaće.

Firefox constantly consumes processor cycles

  • 2 wotmołwje
  • 2 matej tutón problem
  • 1 napohlad
  • Poslednja wotmołwa wot brainchild

brainchild
brainchild
more options

When I have about 15 tabs open, Firefox uses processor cycles continuously. Concretely, usage is about 10% on my new Inspiron 11 3000 with a quad-core Pentium. The effect persists even when Firefox runs in safe mode and when none of the open sites have advertisement. It also persists when the NoScript plugin is in use to prevent execution of extraneous JavaScript.

Minimizing all windows appears to alleviate the problem substantially, though I don't like to do this because it causes thumbnail representations of the windows to be lost.

Note that my environment is Firefox v32 running under Ubuntu 14.04, as seen in the automatically provided troubleshooting information.

What might explain the effect described above, and how can I achieve the more acceptable level of demand for processor power observed when windows are minimized, without actually minimizing all windows?

When I have about 15 tabs open, Firefox uses processor cycles continuously. Concretely, usage is about 10% on my new Inspiron 11 3000 with a quad-core Pentium. The effect persists even when Firefox runs in safe mode and when none of the open sites have advertisement. It also persists when the NoScript plugin is in use to prevent execution of extraneous JavaScript. Minimizing all windows appears to alleviate the problem substantially, though I don't like to do this because it causes thumbnail representations of the windows to be lost. Note that my environment is Firefox v32 running under Ubuntu 14.04, as seen in the automatically provided troubleshooting information. What might explain the effect described above, and how can I achieve the more acceptable level of demand for processor power observed when windows are minimized, without actually minimizing all windows?

Wšě wotmołwy (2)

guigs
guigs
more options

Brainchild, perhaps the feature in Options "Do not load tabs until selected"?

brainchild
brainchild Prašer
more options

In fact, that option is already enabled.