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!

Spletno mesto bo delovalo z omejenimi zmožnostmi, medtem ko na njem izvajamo vzdrževalna dela za vas. Če članki ne rešijo vaše težave in želite zastaviti vprašanje, naša skupnost za podporo čaka na vas na @FirefoxSupport na Twitterju in na /r/firefox na Redditu.

Avatar for Username

Iskanje po podpori

Izogibajte se prevarantski tehnični podpori. Nikoli vam ne bomo naročili, da pokličete telefonsko številko ali nam pošljete osebne podatke. Sumljivo dejavnost prijavite z gumbom »Prijavi zlorabo«.

Več o tem

Ta tema je arhivirana. Postavite prosim novo vprašanje, če potrebujete pomoč.

heavy disk activty from FF 11 on after a reboot

  • 1 odgovor
  • 5 ima to težavo
  • 4 ogledi
  • Zadnji odgovor od Tristan C.

elvado1
elvado1
more options

After I reboot the computer and restart FF 11 it slams the disk. I know it ff because that what shows up in the resource monitor. For example I started ff after rebooting just now and the disk activity has been basically 100% for the last 30 minutes and it's all attributed to FF. From what I can tell from the resource monitor it's reading from and writing to caches in my FF profile.

After I reboot the computer and restart FF 11 it slams the disk. I know it ff because that what shows up in the resource monitor. For example I started ff after rebooting just now and the disk activity has been basically 100% for the last 30 minutes and it's all attributed to FF. From what I can tell from the resource monitor it's reading from and writing to caches in my FF profile.

Vsi odgovori (1)

Tristan C.
Tristan C.
more options

Hello elvado1,

I'm sorry to hear that you are facing issues with the disk usage on Firefox, but have noticed that you are using an outdated version of the web browser. You might want to upgrade to the latest version (12.0), which can be found here, as this might be a bug only affecting the release you are currently using. Please let me know how that works out for you.

Thank you for your valuable time and patience, and please mark this answer as solution if you found it helpful.