搜索 | 用户支持

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

详细了解

When FF restarts after a crash, why does it not restore my previous session?

  • 3 个回答
  • 3 人有此问题
  • 5 次查看
  • 最后回复者为 bsfinkel

more options

Firefox crashed twice today (on the same URL), and each time it restarted, it did not honor my option to "restore the previous session". Each time it restarted with one window, I checked my options, and the "restore previous session" option was still set. The happened last week also. FF 32.0, Windows 7 Professional 32-bit. Thanks.

--Barry Finkel

Firefox crashed twice today (on the same URL), and each time it restarted, it did not honor my option to "restore the previous session". Each time it restarted with one window, I checked my options, and the "restore previous session" option was still set. The happened last week also. FF 32.0, Windows 7 Professional 32-bit. Thanks. --Barry Finkel

所有回复 (3)

more options

Hi Barry, can you use History > Restore Previous Session?

I think you need to fix this setting:

(1) In a new tab, type or paste about:config in the address bar and press Enter. Click the button promising to be careful.

(2) In the search box above the list, type or paste sess and pause while the list is filtered

(3) Double-click browser.sessionstore.resume_from_crash to switch it from false to true

You might also want to reset or at least increase these values, but based on our earlier thread, perhaps these would make your session history less stable:

browser.sessionstore.max_windows_undo is currently zero

browser.sessionstore.max_tabs_undo is currently zero

more options

Since you have Advanced SystemCare, you may find that some Firefox edits are reverted. You may need to turn off the settings protections feature(s) of ASC.

more options

I have toggled browser.sessionstore.resume_from_crash from false to true, and I will see what happens after the next crash. I did not increase the other two parameters from 0.

I again disabled the ASC Surfing Protection Addon. I had disabled it on August 17, but somehow it got re-enabled.

--Barry Finkel