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

Since the latest update (to 44.0, on win7), FF has been consuming nearly every available clock cycle - 60%-70% on my 6-core, 3.5GHz machine. Why?!??

  • 1 wotmołwa
  • 1 ma tutón problem
  • 2 napohladaj
  • Poslednja wotmołwa wot FredMcD

more options

Since the latest update (to 44.0, on win7), FF has been keeping my cpu "pegged" (eating 60%-70% on my 6 core, 3.5GHz machine. IMO, this should *never* happen and is at least, at *some* level, a major regression. I do keep many window/tabs open but, it's never been this bad before. This is while no videos are playing (though I expect there's plenty of javascript running "quietly" on many pages, as is the way of the web these days). Is this a "known issue", is it being addressed (hopefully) ?

Since the latest update (to 44.0, on win7), FF has been keeping my cpu "pegged" (eating 60%-70% on my 6 core, 3.5GHz machine. IMO, this should *never* happen and is at least, at *some* level, a major regression. I do keep many window/tabs open but, it's never been this bad before. This is while no videos are playing (though I expect there's plenty of javascript running "quietly" on many pages, as is the way of the web these days). Is this a "known issue", is it being addressed (hopefully) ?

Wšě wotmołwy (1)

more options