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!

Die Funktionalität dieser Website ist durch Wartungsarbeiten eingeschränkt, die Ihr Erlebnis verbessern sollen. Wenn ein Artikel Ihr Problem nicht löst und Sie eine Frage stellen möchten, können Sie unsere Gemeinschaft über @FirefoxSupport auf Twitter, /r/firefox oder Reddit fragen.

Avatar for Username

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Dieses Thema wurde archiviert. Bitte stellen Sie eine neue Frage, wenn Sie Hilfe benötigen.

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

  • 1 Antwort
  • 1 hat dieses Problem
  • 13 Aufrufe
  • Letzte Antwort von 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?

Alle Antworten (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.