為了改善您的使用體驗,本網站正在進行維護,部分功能暫時無法使用。若本站的文件無法解決您的問題,想要向社群發問的話,請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問,我們的社群成員將很快會回覆您的疑問。

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

FF crashes due to SessionStore

  • 1 回覆
  • 1 有這個問題
  • 4 次檢視
  • 最近回覆由 OldAcer

more options

FF 45.2 ESR (latest that will install on this machine with Lucid 5.2.8 Linux) sometimes froze the system, more often crashed without any error message or from any particular action, except being more common with busy ad-laden sites. Crash Reporter has never ever made a report on this system. The FF crash will sometimes take down unrelated text-editing or image-viewing X-windows. Restarting FF (without reboot) sometimes works but sometimes causes another crash while loading the "Sesssion Restore" tab (without any IP connection). Usually 2nd or 3rd FF restarts (no reboot) allow continued operation, if no tabs from Session Restore are activated.

However, in a recent case, starting FF after multiple reboots from system CD and no internet connection would cause immediate crash while loading the Session Resore tab, even if one attempted to stop that tab. Removing "...default/sessionstore-backups" and ".../sessionstore.bak" and ".../sessionCheckpoints.json" allowed FF to run.

Any idea how the session restore procedure could cause repeatable crashes? Not familiar enough with Linux to know how to start FF under a trace procedure, but can put back the suspect files. Is there documentation on how to read those files in an editor?

FF 45.2 ESR (latest that will install on this machine with Lucid 5.2.8 Linux) sometimes froze the system, more often crashed without any error message or from any particular action, except being more common with busy ad-laden sites. Crash Reporter has never ever made a report on this system. The FF crash will sometimes take down unrelated text-editing or image-viewing X-windows. Restarting FF (without reboot) sometimes works but sometimes causes another crash while loading the "Sesssion Restore" tab (without any IP connection). Usually 2nd or 3rd FF restarts (no reboot) allow continued operation, if no tabs from Session Restore are activated. However, in a recent case, starting FF after multiple reboots from system CD and no internet connection would cause immediate crash while loading the Session Resore tab, even if one attempted to stop that tab. Removing "...default/sessionstore-backups" and ".../sessionstore.bak" and ".../sessionCheckpoints.json" allowed FF to run. Any idea how the session restore procedure could cause repeatable crashes? Not familiar enough with Linux to know how to start FF under a trace procedure, but can put back the suspect files. Is there documentation on how to read those files in an editor?

所有回覆 (1)

more options

Note that a FF crash (FF window disappears) never takes out all windows, even if it takes out a window started after FF.