Closed
Bug 641258
Opened 15 years ago
Closed 12 years ago
Error "Invalid URL" on cancel session recovery
Categories
(Firefox :: Session Restore, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: znerd, Unassigned)
Details
Attachments
(2 files)
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0) Gecko/20100101 Firefox/4.0
Build Identifier: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0) Gecko/20100101 Firefox/4.0
I started Firefox after (apparently) crashing it (by shutting down the computer without waiting for Firefox to terminate?)
Firefox shows the option to revive my old session or cancel; but when I press Cancel it gives an odd error saying: The URL is invalid and cannot be loaded.
Reproducible: Didn't try
Steps to Reproduce:
1. Start Firefox.
2. Have one page open.
3. Shut down Firefox without properly shutting it down. (kill -9 or so)
4. Restart Firefox
5. Press [Cancel] on the page that asks whether you want to revive your session.
Actual Results:
Error: The URL is invalid and cannot be loaded.
Expected Results:
My homepage.
Workaround is just to type some URL in the URL bar.
| Reporter | ||
Comment 1•15 years ago
|
||
Comment 2•15 years ago
|
||
Works for me using Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0) Gecko/20100101 Firefox/4.0.
Could you please check to see if you can reproduce this issue? In the case it's reproducible, if you could attach your sessionstore.js (in your profile folder) that would help finding the problem.
| Reporter | ||
Comment 3•15 years ago
|
||
For me it is reproducible. Attached is my sessionstore.js file.
Updated•15 years ago
|
Version: unspecified → 4.0 Branch
Comment 4•12 years ago
|
||
Ernst, can you still reproduce?
Component: General → Session Restore
Flags: needinfo?(znerd)
| Reporter | ||
Comment 5•12 years ago
|
||
Nope, not reproducible anymore with Firefox 26.0 on OS X 10.9.1.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Flags: needinfo?(znerd)
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•