搜尋 Mozilla 技術支援網站

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

了解更多

Restore Session list of tabs and windows blank?

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

more options

Shortly after upgrading to Firefox 56.0.2 64-bit the browser became unresponsive. After using Task Manager (Windows 10) to terminate and relaunching it, the Restore Session page was displayed with a blank list of tabs and windows (see first attached image).

Any idea what caused this to occur?

Tried following instructions to use files in sessionstore-backups folder to restore tabs, but strangely the files are either too old or seem too small in size (see second attached image).

Any way to retrieve my approximately 30 lost tabs?

Shortly after upgrading to Firefox 56.0.2 64-bit the browser became unresponsive. After using Task Manager (Windows 10) to terminate and relaunching it, the Restore Session page was displayed with a blank list of tabs and windows (see first attached image). Any idea what caused this to occur? Tried following instructions to use files in sessionstore-backups folder to restore tabs, but strangely the files are either too old or seem too small in size (see second attached image). Any way to retrieve my approximately 30 lost tabs?
附加的畫面擷圖

由 pseudonymo 於 修改

所有回覆 (3)

more options

This can happen if you use CCleaner to clear Firefox's session data. So try to remove session for Firefox in CCleaner if you use this software.

more options

pseudonymo said

Tried following instructions to use files in sessionstore-backups folder to restore tabs, but strangely the files are either too old or seem too small in size (see second attached image).

The files with lz4 in the name are compressed, so it's normal for them to be much smaller than the uncompressed files used in Firefox 55 and before.

Try viewing the contents of the 10/29/2017 file using this tool on my website:

https://www.jeffersonscher.com/res/scrounger.html

Does that one have some of what you need? You can save a list of clickable links as a workaround.

more options

That did the trick, specifically scrounging the compressed upgrade backup file upgrade.jsonlz4-20171024165158.

Thanks very much for your help!