Funkcionalnosć toś togo sedła se pśez wótwardowańske źěła wobgranicujo, kótarež maju wašo dožywjenje pólěpšyś. Jolic nastawk waš problem njerozwězujo a cośo pšašanje stajiś, wobrośćo se na našo zgromoźeństwo pomocy, kótarež na to caka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomagaś.

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

Why is FFox such a memory hog

  • 1 wótegrono
  • 0 ma toś ten problem
  • 5 naglědow
  • Slědne wótegrono wót jonzn4SUSE

more options

I was typing in Word and noticed that the keystrokes were lagging. I checked Task Manager and found that I had 84% memory usage, over 600 MB, almost 12% due to FFox. I closed it and reopened it and same thing. I had only 1 tab open, Google News. I tried Chrome and it only used 175 MB and Edge about 300 MB. Furthermore, that single page caused 13 instances of FFox in Task Manager. Why is FFox such a memory hog?

I have a Surface GO with 8MB RAM and a 256 GB SSD that is 60% full running Win 10 Pro 22H2.

I was typing in Word and noticed that the keystrokes were lagging. I checked Task Manager and found that I had 84% memory usage, over 600 MB, almost 12% due to FFox. I closed it and reopened it and same thing. I had only 1 tab open, Google News. I tried Chrome and it only used 175 MB and Edge about 300 MB. Furthermore, that single page caused 13 instances of FFox in Task Manager. Why is FFox such a memory hog? I have a Surface GO with 8MB RAM and a 256 GB SSD that is 60% full running Win 10 Pro 22H2.

Wšykne wótegrona (1)

more options