X
Tap here to go to the mobile version of the site.

Support Forum

browser.cache.check_doc_frequency=2 not working. How to fix?

Posted

When I start Firefox I want it to load the cached version of my tabs. It used to do this, but now it refreshes the tabs when it starts up. I have tried starting in safe mode and it also refreshes the tabs when it starts. I have set browser.cache.check_doc_frequency=2, so it should us the cached to load the tabs, but it is not. This change only happened in the last few month.

When I start Firefox I want it to load the cached version of my tabs. It used to do this, but now it refreshes the tabs when it starts up. I have tried starting in safe mode and it also refreshes the tabs when it starts. I have set browser.cache.check_doc_frequency=2, so it should us the cached to load the tabs, but it is not. This change only happened in the last few month.

Chosen solution

Does Firefox create a sessionstore.js file when you close Firefox and are the backups in the sessionstore-backups folder present?

previous.js (cleanBackup: copy of sessionstore.js from previous session that was loaded successfully)
recovery.js (latest version of the sessionstore written during runtime)
recovery.bak (previous version of the sessionstore written during runtime)
upgrade.js-<build_id> (backup created during an upgrade of Firefox)

Create a new profile as a test to check if your current profile is causing the problem.

See "Creating a profile":

If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over problems.

Read this answer in context 0

Additional System Details

Installed Plug-ins

  • Gecko Media Player 1.0.9Video Player Plug-in for QuickTime, RealPlayer and Windows Media Player streams using MPlayer
  • Version: 5.41.0.0
  • Shockwave Flash 11.2 r202
  • Version 2.1.5 Rincewind, copyright 1996-2012 VideoLAN and Authorshttp://www.videolan.org/vlc/

Application

  • Iceweasel 38.0.1
  • User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0 Iceweasel/38.0.1
  • Support URL: https://support.mozilla.org/1/firefox/38.0.1/Linux/en-US/

Extensions

  • Adblock Plus 2.6.9.1-signed ({d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d})
  • Beef Taco (Targeted Advertising Cookie Opt-Out) 1.3.7.1-signed (john@velvetcache.org)
  • BetterPrivacy 1.68.1-signed ({d40f5e7b-d2cf-4856-b441-cc613eeffbe3})
  • BugMeNot Plugin 3.1-signed ({987311C6-B504-4aa2-90BF-60CC49808D42})
  • Character Identifier 0.1.4.1-signed (char-identifier@dbaron.org)
  • Classic Theme Restorer 1.3.4 (ClassicThemeRestorer@ArisT2Noia4dev)
  • Download YouTube Videos as MP4 1.8.3.1-signed ({b9bfaf1c-a63f-47cd-8b9a-29526ced9060})
  • FacebookBlocker 1.2.2 (facebookBlocker@webgraph.com)
  • Flash and Video Download 1.73 ({bee6eb20-01e0-ebd1-da83-080329fb9a3a})
  • Flashblock 1.5.18.1-signed ({3d7eb24f-2740-49df-8937-200b1cc08f8a})
  • Ghostery 5.4.5.1-signed (firefox@ghostery.com)
  • Google Translator for Firefox 2.1.0.5.1 (translator@zoli.bod)
  • Greasemonkey 3.2 ({e4a8a97b-f2ed-450b-b12d-ee082ba24781})
  • HTTPS-Everywhere 5.0.5 (https-everywhere@eff.org)
  • IDND 1.6.5.1-signed ({9757e92f-94d4-4b02-ba2d-0454955c7e4b})
  • Image Zoom 0.6.3.1-signed ({1A2D0EC4-75F5-4c91-89C4-3656F6E44B68})
  • ImageTweak 0.25.1.1-signed ({DB2EA31C-58F5-48b7-8D60-CB0739257904})
  • It's All Text! 1.9.1 (itsalltext@docwhat.gerf.org)
  • Jump Link 1.3.2 ({5CEC528D-624F-4b07-9990-D436F02B28AA})
  • Leet Key 1.4.3.1-signed.1-signed ({3335F91D-2AEF-4097-B831-C96C60349822})
  • Link Visitor 4.0.1.1-signed ({9C013B6E-46FC-11DD-B644-FC4D56D89593})
  • Linky 3.0.0.1-signed (linky@gemal.dk)
  • Monkeysphere 0.8 (tls-xul-ext@monkeysphere.info)
  • NoScript 2.6.9.29 ({73a6fe31-595d-460b-a920-fcc0f8843232})
  • RequestPolicy Continued 0.5.29b4 (rpcontinued@requestpolicy.org)
  • Rotate Image 0.1.3.2.1-signed (rotateimage@minisystems.de)
  • Saved Password Editor 2.9.1-signed (savedpasswordeditor@daniel.dawson)
  • Social Fixer 7.701 (socialfixer@mattkruse.com)
  • Status-4-Evar 2015.02.06.23.1-signed (status4evar@caligonstudios.com)
  • Stylish 2.0.2.1-signed ({46551EC9-40F0-4e47-8E18-8E5CF550CFB8})
  • text/plain 1.1.9.2.1-signed ({e1c8879e-9db4-4adf-92d2-d4856bd434ef})
  • Text2Link 1.9.8.1-signed ({E9AE265A-1885-4143-BDC3-2783D9124418})
  • Uncheck Stay-signed-in for Google Login 1.2.1-signed (jid0-mkbYJnyD0AUFscw1E6PD2ItAIzU@jetpack)
  • User Agent Switcher 0.7.3.1-signed ({e968fc70-8f95-4ab9-9e79-304de2a71ee1})
  • YouTube ALL HTML5 2.1.3.1-signed (jid1-qj0w91o64N7Eeg@jetpack)
  • ErrorZilla 0.2 ({e1ce8a25-733c-4183-883f-0b826e9dbf77}) (Inactive)
  • Firebug 2.0.11 (firebug@software.joehewitt.com) (Inactive)

Javascript

  • incrementalGCEnabled: True

Graphics

  • adapterDescription: X.Org -- Gallium 0.4 on AMD CAICOS
  • adapterDeviceID: Gallium 0.4 on AMD CAICOS
  • adapterDrivers:
  • adapterRAM:
  • adapterVendorID: X.Org
  • driverDate:
  • driverVersion: 3.0 Mesa 10.5.8
  • info: {u'AzureCanvasBackend': u'cairo', u'AzureFallbackCanvasBackend': u'none', u'AzureContentBackend': u'cairo', u'AzureSkiaAccelerated': 0}
  • numAcceleratedWindows: 0
  • numAcceleratedWindowsMessage: [u'']
  • numTotalWindows: 1
  • webglRenderer: X.Org -- Gallium 0.4 on AMD CAICOS
  • windowLayerManagerRemote: False
  • windowLayerManagerType: Basic

Modified Preferences

Misc

  • User JS: Yes
  • Accessibility: No
cor-el
  • Top 10 Contributor
  • Moderator
17669 solutions 159836 answers

Helpful Reply

Did you check on the about:cache page that the disk cache is used and working?

In case you use "Clear history when Firefox closes" make sure not to clear the Cache.

Did you check on the about:cache page that the disk cache is used and working? In case you use "Clear history when Firefox closes" make sure not to clear the Cache.

Question owner

about:cache shows,

Number of entries: 16249 Maximum storage size: 358400 KiB Storage in use: 316690 KiB

for disk. That looks in use.


The "Clear history when Firefox closes" is not checked.

about:cache shows, Number of entries: 16249 Maximum storage size: 358400 KiB Storage in use: 316690 KiB for disk. That looks in use. The "Clear history when Firefox closes" is not checked.
cor-el
  • Top 10 Contributor
  • Moderator
17669 solutions 159836 answers

Chosen Solution

Does Firefox create a sessionstore.js file when you close Firefox and are the backups in the sessionstore-backups folder present?

previous.js (cleanBackup: copy of sessionstore.js from previous session that was loaded successfully)
recovery.js (latest version of the sessionstore written during runtime)
recovery.bak (previous version of the sessionstore written during runtime)
upgrade.js-<build_id> (backup created during an upgrade of Firefox)

Create a new profile as a test to check if your current profile is causing the problem.

See "Creating a profile":

If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over problems.

Does Firefox create a sessionstore.js file when you close Firefox and are the backups in the sessionstore-backups folder present? previous.js (cleanBackup: copy of sessionstore.js from previous session that was loaded successfully) recovery.js (latest version of the sessionstore written during runtime) recovery.bak (previous version of the sessionstore written during runtime) upgrade.js-<build_id> (backup created during an upgrade of Firefox) Create a new profile as a test to check if your current profile is causing the problem. See "Creating a profile": *https://support.mozilla.org/kb/profile-manager-create-and-remove-firefox-profiles *http://kb.mozillazine.org/Standard_diagnostic_-_Firefox#Profile_issues If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over problems. *http://kb.mozillazine.org/Transferring_data_to_a_new_profile_-_Firefox

Question owner

It does create the sessionstore.js and the sessionstore-backups files.

I created a new profile. Set it "Show windows and tabs from last time" and changed browser.cache.check_doc_frequency to 2, so it should always use the cache version. I then opened several tabs. A couple were ones that change fairly regularly. (news sites that post new stories.) I closed the browser and waited. Then opened the browser and it went and refreshed the tabs instead of using the cache. I could tell because a new story was showing that was not in the cached version. So the new profile didn't solve the issue.

It does create the sessionstore.js and the sessionstore-backups files. I created a new profile. Set it "Show windows and tabs from last time" and changed browser.cache.check_doc_frequency to 2, so it should always use the cache version. I then opened several tabs. A couple were ones that change fairly regularly. (news sites that post new stories.) I closed the browser and waited. Then opened the browser and it went and refreshed the tabs instead of using the cache. I could tell because a new story was showing that was not in the cached version. So the new profile didn't solve the issue.

Question owner

It appears I was a bit hasty checking the new profile and it did actually fix the issue. I've copied over about 90% of the old profile while checking that the fix was still working. I have all the plugins, signons, config, even the session history. I did try to have a cleaner profile by leaving behind file that seem to no longer be used. So bookmark backup and other backup files stayed behind as well as what seemed to be obsolete extensions.

The new profile works, though carefully coping and checking that the copied files didn't cause the problem in the new profile is tedious.

It appears I was a bit hasty checking the new profile and it did actually fix the issue. I've copied over about 90% of the old profile while checking that the fix was still working. I have all the plugins, signons, config, even the session history. I did try to have a cleaner profile by leaving behind file that seem to no longer be used. So bookmark backup and other backup files stayed behind as well as what seemed to be obsolete extensions. The new profile works, though carefully coping and checking that the copied files didn't cause the problem in the new profile is tedious.