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“.

Learn More

When I open FF 57.0.4, Tabs that I closed and do not intend to re-open when starting up FF again do indeed re-open! HELP!?

  • 21 Antworten
  • 2 haben dieses Problem
  • 3 Aufrufe
  • Letzte Antwort von larrygreen1886

more options

I have over 30 pinned tabs and 2 regular tabs open when I open FF. I close the 2 regular tabs and then exit FF only to re-open FF and the 2 regular tabs have returned!

Why is this and how can I make it stop doing this?

I have over 30 pinned tabs and 2 regular tabs open when I open FF. I close the 2 regular tabs and then exit FF only to re-open FF and the 2 regular tabs have returned! Why is this and how can I make it stop doing this?

Alle Antworten (1)

more options

jscher2000 said

According to some bug reports, sometimes Firefox 56-59 stops being able to update the recovery.jsonlz4 file due to a problem with a background process (a promise worker process). Firefox 58 (due out next week) will contain some fixes for this that hopefully will solve the problem for most people. If anyone experiences the issue after that, it would be helpful to check the Browser Console for errors messages along these lines: Could not write session state file Object { operation: "move", path: "C:\Users\user\AppData\Roaming\Mozilla\Firefox\Profiles\1a2b3c4d.default\sessionstore-backups\recovery.jsonlz4", winLastError: 5, stack: "", fileName: "(unknown module)", lineNumber: undefined } SessionFile.jsm:396 That could indicate another variation on the problem that Firefox needs to detect and correct for.

Thanks for this information. Funny because after I mentioned that the problem was still occurring after changing style rules, it somehow disappeared by the next day and has been loading correctly ever since. Good to know that the underlying issue will be fixed next release though.

  1. 1
  2. 2