Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox 17 always opens the tabs that were open the last time I closed it. I do NOT use restore history.

  • 7 replies
  • 5 have this problem
  • 668 views
  • Last reply by kdock

more options

This has started happening since I upgraded to v.17. I close Firefox either with the Red X or the exit button on the dropdown menu. The next time I open, it displays whatever pages were open when I closed it.

I have always had Firefox use my Google account as my home page. It will not display.

It seems to me that in your quest to keep updated (how many this year...?) that you've lost a little something. This is very bad behavior and I'll just stop using FF altogether if it isn't fixed soon.

Chosen solution

Well, I rolled back two versions to the FF15 just before 16 came out. It still works with the latest NIS, and it does not exhibit the behavior I complained about in my original question.

It could be that FF17 thought it had crashed every time I closed it. And that was true no matter how I closed it.

I'm losing faith with Mozilla's R&D, but at least they still host their previous versions if/when the current one doesn't work.

Read this answer in context 👍 1

All Replies (7)

more options

Make sure that Firefox closes properly and that there are no hanging Firefox processes left in the task manager.
It is usually best to use the Exit item in the Firefox or File menu to close Firefox.

See:

You can check for problems with the files sessionstore.js and sessionstore.bak in the Firefox Profile Folder that store session data.

Delete the sessionstore.js file and possible sessionstore-##.js files with a number and sessionstore.bak in the Firefox Profile Folder.

Deleting sessionstore.js will cause App Tabs and Tab Groups and open and closed (undo) tabs to get lost, so you will have to create them again (make a note or bookmark them).

more options

Hi Cor-el and thanks for your reply.

Re: hangs -- FF doesn't hang at exit; it sporadically hangs when I right click on a link and open the link in a new tab.

Re: restoring tabs -- Deleting sessionstore.js and related session files did not help. I opened several tabs, closed FF and deleted all the session files, then opened. FF reopened all the tabs.

UPDATE** I left out the .bak session file in my first deletion. Once that was deleted, FF opened on my default page. Still, I'd love to know why this suddenly started happening when I updated to FF 17...

UPDATE TO UPDATE** Unfortunately, it didn't stick. The very next time I opened FF, it opened with the last two tabs I had open. I suspect the .bak file may be the key here, but I think I'll downgrade and wait until this works a little better.

Modified by kdock

more options

the answer to this question might also help: https://support.mozilla.org/questions/942651

more options

Unfortunately, it didn't help.

I made the change, closed FF with three tabs appearing. Using the Firefox drop-down, it clicked Exit. Waited. Then opened. All three tabs appeared and no hint of a "different screen." I don't think this is my issue.

Thanks.

more options

Which security software (firewall, anti-virus) do you have?

Some security software has virtualization or sandbox features that may cause problems by protecting and restoring files in the Firefox profile folder.

more options

Norton Internet Security all patched up. But is this a new feature -- something NIS would have started doing immediately after I installed FF17?

I waited to install FF17 because of NIS toolbar issues.

more options

Chosen Solution

Well, I rolled back two versions to the FF15 just before 16 came out. It still works with the latest NIS, and it does not exhibit the behavior I complained about in my original question.

It could be that FF17 thought it had crashed every time I closed it. And that was true no matter how I closed it.

I'm losing faith with Mozilla's R&D, but at least they still host their previous versions if/when the current one doesn't work.