Hi

thank you for contacting support. That's weird that you're browser opens without the oops page. 

If I may ask, how old is the sessionrestore.js file, and is this

browser.sessionstore.resume_from_crash.

set to false in the about:config page? and what is the homepage setting, is it show tabs from last time? And what happened right before the crash?

Looking forward to your reply!

Hi, thanks for your reply! Yes, FF had crashed from time to time before but this time, I didn't get the oops page.

Here's your answers:

I can't tell you how old sessionREstore.js is because it's not there. I have 3 sessionstore files - sessionstore (no .js) dated 12/19/13, which I'm guessing has just the 25 tabs in it, sessionstore.bak-20131112160018 from 11/17/13 and sessionstore.bak from 12/19/13. No sessionrestore file.

browser.sessionstore.resume_from_crash appears to be set to False.

Home page is restore tabs from last time.

Right before the crash, FF slowed down to a crawl, showed Not Responding for a while, recovered, and then I tried to close it to open it back up again. I had estimated 150 tabs open. It took a long time to close and when I reopened it, there was no "oops" and about 25 of the tabs furthest to the left (oldest) opened.

Thank you very much!

Hi,

Thank you for your message as well. That option in about:config, if it is set to false the oops page will not show up, if you would like this to set it to true for future recoveries if you would like.

This previous question has a few options to restore the 150 tabs, however I am not sure if it will work if the sessionrestore.js file is not there: https://support.mozilla.org/en-US/que.../975598

The option show tabs from last time may have a limit, but I am not sure, let me check if there is a default.

This was pretty handy as well when I was looking: http://mzl.la/MCnd4M That kb shows that it may just be as easy as renaming the .bak file to .js, however please save a copy of the file before renaming it so that it does not become corrupt. Because it crashed it cannot be sure that it is not corrupt. The .bak file will only be from the last time firefox was open. Each time firefox is opened the file will be overwritten, so just to warn you the 150 tabs may not be there if you have closed it since it reopened after the crash.

Hope this helps!

I think this is the one for keeping track of the last closed tabs.... http://kb.mozillazine.org/Browser.sessionstore.max_tabs_undo

However this will change on the next session if this is not set. The other thing I found was that there is an api that allows extensions to keep track of the ref https://developer.mozilla.org/en-US/d.../Session_store_API

There might be an add on or extension out there to help with all those tabs you keep open. Best of luck, if there are any other questions we are happy to help.

Thanks.

I used to get the oops page and did nothing to change the setting. The system changed it all by itself.

Ok, this is weird, I checked again and it's set to True. I'm sure it said false before.

It would seem that the real issue is how do I get sessionrestore.js back? I didn't delete it. Do I rename another file? A sessionstore file?

There is a bug here that I am very sure changed the above setting and deleted the sessionrestore.js file.

Is the browser corrupted?

I would really like to know what the maximum number of tabs can be open and the number where performance starts to drag. I do know that with the number I had open, it would take a few minutes for the browser to close.

thanks again!

So some sources say it depends on the amount of Ram and to alleviate this it can be set to not automatically load background tabs in the tab settings of the browser. (In Preferences or Options for Windows).

There is no limit though, so it may have been a memory issue. When it stopped working, it may have reached the max. [Ref satdav and tad and tyler]

However, the setting changing I do not know about. Troubleshooting preferences that will not save is a good resource: How to fix preferences that won't save

In order to get the session back you can change the most recent file with the extension ".bak" to ".js" but the file will have been overwritten if it was reopened after the first opening where the 25 tabs were.

Yeah I already had the setting to not load the tab data, just the tab itself. I have plenty of RAM (I thought) but that makes sense.

I can change the most recent .bak file to .js, but I 'don't have a sessionrestore.js file to change the extension.

All I have is sessionstore files per the above.

I think I've created a new bug that is not addressed in the KB.

Note that Windows hides some file extensions by default.
Among them are .html and .ini and .js and .txt, so you may only see a sessionstore name without file extension.
You can see the real file extension (type) if you open the Properties of the file via the right-click context menu.