Insufficient time for reopening session may give error message.

RESOLVED INCOMPLETE

Status

()

Firefox
Session Restore
RESOLVED INCOMPLETE
8 years ago
4 years ago

People

(Reporter: Keith Alderson, Unassigned)

Tracking

3.6 Branch
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [DUPEME])

(Reporter)

Description

8 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 (.NET CLR 3.5.30729)

The error message suggesting removing pages from session restore may not initially be required.
When I reopen a session I always get this message and used to give up at this point since removing pages did not seem to help.  However when ignoring this error message eventually the pages all open.
Perhaps an alternative error message or different instructions could allow the system more time.  Or perhaps the system could be changed to open one page at a time.

Reproducible: Always

Steps to Reproduce:
1.Opened firefox after forced closure
2.Restored session fails and gives suggestion to cut out some pages - of course although I have no idea which pages might have failed all I can do is close them one by one, trying to remember which relates to which information I want to look at again on the web sites (THIS IS THE REASON FOR THE SESSION RESTORE).
3.Even closing pages did not allow the other pages to open.
4.Using restore seemed pointless so I stopped using firefox - other browsers do cope with restoring.
5.At some point I just ignored the error message - the pages DO eventually load.

6.Changing the error message OR the time sequences in the opening program may enable others to use the restore feature.
TKS Keith.
So this error message (assuming you mean the "oops..." message) is only supposed to show up after a couple consecutive crashes. Usually this happens when a single page has something that crashes, so reloading it would just cause Firefox to crash again. If it was a different message, than it is an extension causing that message, not Firefox.

Regardless, if you get the built in Firefox "oops" screen, then you can just press restore and all of your pages should restore. It's possible that connections timeout and pages do fail to restore (but that's a connection issue, not necessarily Firefox's fault and could happen with other browsers as well). Some of it may be performance related (see bug 394492), but there are things we might be able to do there. I think there's a bug on making the message more clear (since it's not necessarily that the pages couldn't be restored), but I can't find it right now.
Whiteboard: [DUPEME]
(Reporter)

Comment 2

8 years ago
The inability to restore session is after the computer has been restarted.
It may be just firefox jumping the gun with the error message - this is the one in the box with various web addresses in a list with a check box against each one, with the suggestion that one or more of the sites could be preventing the restore.
Not sure why firefox itself cannot just dump offending web addresses then open all working ones,finally listing those even a second attempt can't open.
Keith.

Updated

7 years ago
Version: unspecified → 3.6 Branch

Comment 3

4 years ago
What is the exact wording of this error message?
DOes it still occur?
Flags: needinfo?(keithalderson100)
Whiteboard: [DUPEME] → [closeme 2014-02-15][DUPEME]

Comment 4

4 years ago
Resolved per whiteboard
Status: UNCONFIRMED → RESOLVED
Last Resolved: 4 years ago
Flags: needinfo?(keithalderson100)
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2014-02-15][DUPEME] → [DUPEME]
You need to log in before you can comment on or make changes to this bug.