We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

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

Toś ta nitka jo se archiwěrowała. Pšosym stajśo nowe pšašanje, joli trjebaśo pomoc.

FF version 34.0.5 -- recovery.js is not being updated during Firefox use, and sessionstore.js does not exist

  • 2 wótegronje
  • 2 matej toś ten problem
  • 2 naglěda
  • Slědne wótegrono wót lie-group

lie-group
lie-group
more options

Beginning approximately two weeks ago I found that (with an earlier version of Firefox) the sessionstore.js file was not being updated during Firefox use. Restarting Firefox brought back the session, windows and tabs exactly as they had been at browser startup.

I have now upgraded to version 34.0.5, and I see the same symptoms, with these other notes as well:

1. recovery.js in sessionstore.backups remains unchanged during Firefox use 2. if sessionstore.js exists I'm unable to find it.

I have verified that the about:config entry browser.sessionstore.interval remains set to 15000. I see as well an old about:config addition where I defined browser.sessionstore.enabled to True at some point in the past.

I'm very much open to any suggestions whatever to induce Firefox to continually (well, more precisely, at 15-second intervals) update its "memory" of session activity along with keeping track of closed and and newly-open tabs during a session.

Thanks to all, in advance.

Beginning approximately two weeks ago I found that (with an earlier version of Firefox) the sessionstore.js file was not being updated during Firefox use. Restarting Firefox brought back the session, windows and tabs exactly as they had been at browser startup. I have now upgraded to version 34.0.5, and I see the same symptoms, with these other notes as well: 1. recovery.js in sessionstore.backups remains unchanged during Firefox use 2. if sessionstore.js exists I'm unable to find it. I have verified that the about:config entry browser.sessionstore.interval remains set to 15000. I see as well an old about:config addition where I defined browser.sessionstore.enabled to True at some point in the past. I'm very much open to any suggestions whatever to induce Firefox to continually (well, more precisely, at 15-second intervals) update its "memory" of session activity along with keeping track of closed and and newly-open tabs during a session. Thanks to all, in advance.

Wšykne wótegrona (2)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

The browser.sessionstore.enabled pref is no longer used, so you can reset this pref to remove it.

You can try to delete the sessionstore-backups folder to force Firefox to create a new folder to see if that helps. Note that Windows hides the .js extension by default.

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.

Also make sure that your security software isn't causing problems. Boot the computer in Windows Safe Mode with network support (press F8 on the boot screen) as a test.

lie-group
lie-group Pšašaŕ
more options

Thank you for the suggestions. So far I have had time only for one experiment: I saved the sessionstore-backups folder and started Firefox from scratch. FF maintained the recovery.js file in the (new) backups folder, updating it in accordance with the interval set in about:config.

When I terminated that session, a new sessionstore.js file was created in the profile folder, which seems to have been a copy of recovery.js at that time.

Restoring my earlier recovery.js file (from the saved copy of sessionstore-backups), Firefox once again stopped updating the recovery.js file.

It seems, anyway, that the problem is actually within the saved information in the recovery.js file (which dates back to the errors I experienced with sessionstore.js originally).

I'll begin working on a new profile now, and report back when I have results from that test.

Thanks once more.