当サイトはユーザー体験を改善するためのメンテナンスを実施中に機能が制限される予定です。記事を読んでもあなたの問題が解決せず質問をしたい場合は、Twitter の @FirefoxSupport、Reddit の /r/firefox で、サポートコミュニティが皆さんを助けようと待機しています。

Mozilla サポートの検索

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

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 件の返信
  • 2 人がこの問題に困っています
  • 3 回表示
  • 最後の返信者: 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?

すべての返信 (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