搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

Learn More

Irregular Disk Caching on Mac - Where do these files go???

  • 2 回覆
  • 1 有這個問題
  • 34 次檢視
  • 最近回覆由 avalbrec

more options

I've noticed from time to time that Firefox doesn't place cache files in the normal ~/Library/Caches location. On rebooting, I cannot also locate any cache components (like startupCache.*.big) in a "Recovered files" folder in the trash. So in a case like this were the heck do these caches go and how can I get rid of them. I have an SSD that is about half full and the last thing I need is to have it filling up with stupid temporary internet files.

Thanks

I've noticed from time to time that Firefox doesn't place cache files in the normal ~/Library/Caches location. On rebooting, I cannot also locate any cache components (like startupCache.*.big) in a "Recovered files" folder in the trash. So in a case like this were the heck do these caches go and how can I get rid of them. I have an SSD that is about half full and the last thing I need is to have it filling up with stupid temporary internet files. Thanks

所有回覆 (2)

more options

"Recovered files" are temp files that Firefox creates for special purposes including clipboard actions.

See:

You can try to set this pref to true on the about:config page.

  • browser.helperApps.deleteTempFileOnExit = true

You can open the about:config page via the location/address bar. You can accept the warning and click "I accept the risk!" to continue.

由 cor-el 於 修改

more options

cor-el said

"Recovered files" are temp files that Firefox creates for special purposes including clipboard actions. See: You can try to set this pref to true on the about:config page.
  • browser.helperApps.deleteTempFileOnExit = true
You can open the about:config page via the location/address bar. You can accept the warning and click "I accept the risk!" to continue.

Thanks so much for the reply but in this case, as stated in my original, the caches aren't even making it to the Recovered files in the Trash. Am thinking it is more likely it's getting bogged-down in var/vm somewhere.