搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

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!