« Insulting source codeHOWTO take apart and repair an old NES »

Exception "Component is not available" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: file:///usr/lib/firefox/components/nsSessionStore.js :: sss_saveState

Technical, Javascript, 219 words   English (AU) Bookmark and Share

Have you ever encountered this error in Firebug while using FF (Firefox)?

Code:

[Exception... "Component is not available" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)"  location: "JS frame :: file:///usr/lib/firefox/components/nsSessionStore.js :: sss_saveState :: line 1753"  data: no] file:///usr/lib/firefox/components/nsSessionStore.js Line 1753

Follow up:

According to a post on Mozillazine , this started appearing since Firefox 2.0.0.8.

Now, there are many possible causes (and fixes) for this problem, but I have found that if you encounter this error and if it comes from firefox/components/nsSessionStore.js. This means that your session store has been corrupted.

What does session store do? Well, when your browser crashes (or force quit), and you fire it up again, session store will loaded the last saved opened URLs, tabs and http sessions (basically the whole state of the browser it last saved) that were present before FF went belly up. Think Word’s autorecovery. Great feature and FF 3 allows you to save the session when quiting FF, which cant be done with FF 2.x at the moment.

The Fix?

Well I have found that clearing the FF sessions fixes the problem. This means that you simply close FF. I also noticed another symptom with this problem is that it occurs, force quitting Firefox and starting FF again will bring up an older saved state.

Trackback address for this post

This is a captcha-picture. It is used to prevent mass-access by robots.
Please enter the characters from the image above. (case insensitive)

10 comments

  1. Permanent link for this comment Patrick said on
    I've tried your suggestion, and as soon as I restart FF the error comes right back.

    Patrick
  2. Permanent link for this comment Steffen Heinrich said on
    Managed to get rid of these by
    1. setting
    "Tools → Options → Main → Startup → When Firefox starts"

    to "Show my windows and tabs from last time"

    2. changing my behaviour to close FF from the file menu
    before exiting Windows.

    This appearantly leads to a clean save/resume process instead of recovery from an emergency state.
    Whether or not both points are mandatory I dont't know.
  3. Permanent link for this comment Brinley Ang® Email said on
    What you are essentially doing is disabling the auto saving of tabs via sessionStore which fixes the error, but I find it useful (for myself at least) to have the option of recovering tabs if the browser crashes without warning and takes down a dozen tabs from my last google search. Yes, I can probably retrieve the links from history but having the tabs show up by themselves is just much easier
  4. Permanent link for this comment Brinley Ang® Email said on
    Patrick, perhaps check that your default startup page isnt the one causing nsSessionStore to crap up.
  5. Permanent link for this comment Carey Underwood Email said on
    Modify nsSessionStore.js, around line 1896, changing it from:
    this._writeFile(this._sessionFile, oState.toSource());

    to:
    this._writeFile(this._sessionFile, "(" + this._toJSONString(oState) + ")");

  6. Permanent link for this comment Wanabo Email said on
    Just empty the cache of FF. Press CTRL+Shift+Delete. Select all except saved passwords.

    Problem fixed. ;)
  7. Permanent link for this comment Data Shaman Email said on
    Comment #5 solved the issue for me, thanks!
  8. Permanent link for this comment Soup Email said on
    well a huge thanks to Carey Underwood !

    that actually seems to work :-)

    been searching about year for this !
    One can only hope that the Mozilla people actually bring it into Firefox at some point
  9. Permanent link for this comment Juan Garcia said on
    These are the related bugs:
    https://bugzilla.mozilla.org/show_bug.cgi?id=366509
    http://code.google.com/p/fbug/issues/detail?id=502
  10. Permanent link for this comment jeremy Email said on
    Thanks for this! I was tearing my hair out trying to understand what was wrong with my JS and it turns out all I had to do was restart FF.

Leave a comment


Your email address will not be revealed on this site.

Your URL will be displayed.
(Line breaks become <br />)
(Name, email & website)
(Allow users to contact you through a message form (your email will not be revealed.)
This is a captcha-picture. It is used to prevent mass-access by robots.
Please enter the characters from the image above. (case insensitive)
July 2010
Mon Tue Wed Thu Fri Sat Sun
 << <   > >>
      1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30 31  
Brinley Ang

Brinley Ang is a sysadmin, web dev, coder, geek boy, jedi knight fragger, caffine addict, deaf meloncholic and rockstar wannabe. Listens to the sex pistols and a wide assortment of heavy metal.

Make payments with PayPal - it's fast, free and secure!
Search
home | portfolio | blog | links | contact
© 2010 - Brinley Ang
Valid xhtml