FF recently started saving to "Disk Cache", why?
I'm not certain when this started so back-tracing may be problematic?
I'm not sure if this is related? But a few days ago I noticed some sites(notably Youtube) the context menu(I think that's what the right click menu is called?) was very laggy. I tend to not think disk cache would affect this? But it did lead me to notice that my disk cache was now saving.
I installed Session Manager 0.8.1.5( https://addons.mozilla.org/en-US/firefox/addon/session-manager/?src=ss ) about the time I noticed the menu issues. I disable it and FF is still caching to disk. I still haven't ruled Session Manager out though.
In "about:config" I set "browser.cache.disk.enable;false" and it's still caching. and I tried setting "browser.cache.memory.capacity" to 0. But it's not saving the new value and each time I go back it's stays set at "browser.cache.disk.capacity;358400".
I also have Cache Status 0.8.5( https://addons.mozilla.org/en-US/firefox/addon/cache-status/?src=search ) installed, this was how I noticed the disk was caching. I tried using it to set the disk cache to 0kb also. But it's not saving the value either.
I would like to note I had always had a value for "browser.cache.memory.capacity" but it had not been saving, since I had one of FF's(Firefox) settings enable/disabled. Sorry to be unclear, but FF isn't exactly clear on caching itself. I think it is having Firefox set to clear history on exit, that had previously prevented disk from being used?
All Replies (5)
5 views? and probably 3 of them are mine. Where is the support especially after a major update being put out?
Firefox 32 uses a new cache back-end called cache2, so cache related extensions may not work properly and may require an update.
New Firefox HTTP cache now enabled on Nightly builds - mayhemer's blog:
"about:config" & Firefox clearing history on exit are basic functions of FF. And changes not being saved in "about:config" is fairly worrisome. IMO, that is a major bug.
Thank you for your reply, ~ Rex
You can check for problems with preferences.
Delete possible user.js and numbered prefs-##.js files and rename (or delete) the prefs.js file to reset all prefs to the default value including prefs set via user.js and prefs that are no longer supported in the current Firefox release.
There is software like Advanced SystemCare with its Surfing Protection feature that can protect files in the Firefox profile folder against changes. If you have such software then check the settings or uninstall this software.
I will try your suggestions when I get a chance. But this whole thing brings up privacy concerns on saving history, not to mention my issue using disk caching makes FF run very very slowly(relative to not using cache(odd considering how it's supposed to speed things up)). And it makes less and less sense(other than saving sessions) considering how fast internet speeds are getting, calling from cache is just an added function for the processor to perform on page loads.
For anyone following this, I will most likely work on a solution in the next few days pending my work load this week.
Thanks cor-el
~ Rex