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!

Funkcionalnosć toś togo sedła se pśez wótwardowańske źěła wobgranicujo, kótarež maju wašo dožywjenje pólěpšyś. Jolic nastawk waš problem njerozwězujo a cośo pšašanje stajiś, wobrośćo se na našo zgromoźeństwo pomocy, kótarež na to caka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomagaś.

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.

Does Windows XP SP3 limit Firefox from writing to & updating the sessionstore.js file?

  • 1 wótegrono
  • 1 ma toś ten problem
  • 13 naglědow
  • Slědne wótegrono wót cor-el

zislinns
zislinns
more options

After Firefox is launched, the sessionstore.js file will continuously be updated for a period of time that may range from less than 30 minutes to several hours. At that moment, any changes to the tabs or sites on the tabs will not be registered through the sessionstore.js updating process. When Firefox is closed down, it typically crashes and has to be restarted and a tab restore selection has to be made. Firefox will then proceed with a normal opening with all tabs restored to where it was at the time the sessionstore.js file updating ended. The symptoms give the appearance of some limiting parameter which becomes saturated depending on the frequency of tab and website changes during a session. I have checked the cache sizes and they are nowhere near the upper bound setting. Any thoughts?

After Firefox is launched, the sessionstore.js file will continuously be updated for a period of time that may range from less than 30 minutes to several hours. At that moment, any changes to the tabs or sites on the tabs will not be registered through the sessionstore.js updating process. When Firefox is closed down, it typically crashes and has to be restarted and a tab restore selection has to be made. Firefox will then proceed with a normal opening with all tabs restored to where it was at the time the sessionstore.js file updating ended. The symptoms give the appearance of some limiting parameter which becomes saturated depending on the frequency of tab and website changes during a session. I have checked the cache sizes and they are nowhere near the upper bound setting. Any thoughts?

Wšykne wótegrona (1)

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

Are there any numbered sessionstore-##.js files present in the Firefox profile folder?

You can use this button to go to the currently used Firefox profile folder:

  • Help > Troubleshooting Information > Profile Director: Show Folder (Linux: Open Director; Mac: Show in Finder)

Deleting sessionstore.js will cause App Tabs and Tab Groups and open and closed (undo) tabs to get lost and you will have to recreate them (make a note or bookmark them if possible).

Did you check for issues caused by your security software?

Boot the computer in Windows Safe Mode with network support (press F8 on the boot screen) as a test to see if this helps.