391014 - Any Firefox operation maxs out system CPU. Exception error 0x8052000f (NS_ERROR_FILE_TOO_BIG). JS frame::file//nsSessionStore.js

Status: RESOLVED DUPLICATE of bug 351551

(Firefox :: Session Restore, defect)

Description

[David Lieber]

User-Agent:       Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322)
Build Identifier: 2.0.0.6

Ver 2.0.0.6 has been running well on machine for a while.  Now, any operation: browsing to new link, or just typing into a dialogue box causes CPU to max out.  Firefox process is not using the CPU directly, it is calling some sort of System process that burns up the CPU.  When releases, Firefox works normaly until I start typing or browse to new url, etc.

In Error console the following error is observed:
Error: [Exception... "Component returned failure code: 0x8052000f (NS_ERROR_FILE_TOO_BIG) [nsIFileOutputStream.init]"  nsresult: "0x8052000f (NS_ERROR_FILE_TOO_BIG)"  location: "JS frame :: file:///C:/Program%20Files/Mozilla%20Firefox/components/nsSessionStore.js :: sss_writeFile :: line 2026"  data: no]
Source File: file:///C:/Program%20Files/Mozilla%20Firefox/components/nsSessionStore.js
Line: 2026

Troubleshooting attempted:
Ran Firefox in safe mode.  No difference in behavior.  Still hangs up.
Unistalled Firefox and reintalled - no differrence in behavior.  Still hangs.

Filing this bug using IE, with no problem with system or network performance via IE.

Reproducible: Always

Steps to Reproduce:
1.Browse or type into dialogue box causes behavior to repeat
2.
3.

Comment 1

[Jo Hermans]

There's a file called sessionStore.js in your profile (see <http://kb.mozillazine.org/Profile_folder_-_Firefox>) that has a problem. Maybe it's extremely large or write-protected or something ? Anyway, you can safely delete this file (when Firefox is not running). It's constantly rewritten to contain the urls currently on the screen, so that when you crash, you can restart with them (the "restore session" dialog box).

Can you please delete the file, and see if this fixes the problem ? If you're afraid to loose data, you can always rename the file first, so that you can restore it.

Bug 388863 mentions a problem with hundreds or thousands of these files. Bug 351551 (the cause) is supposed to be fixed in 2.0.0.5 however.

Comment 2

[David Lieber]

Deleted file.  Firefox runs ~15% better now.  I no longer get the error msg.  But Firefox has not recreated the file as I thought it would upon next start up.  FYI - the file was only 51K when i deleted it, so it shouldn't have been too big???

Firefox is still not running at an acceptable level.  Every Firefox click causes some System process to max out cpu and renders Firefox unusable for 5-10 seconds per click.  Any other suggestions out there?

Comment 3

[Simon Bünzli]

Are there any further files ending in .moztmp or containing a hyphen and a number (e.g. sessionstore-1.js) inside your profile folder? If so, please delete them as well.

Otherwise, make sure that neither your virus scanner nor your desktop search engine (should you have any) do access sessionstore.js.

If that still doesn't help, try creating a clean profile (see http://kb.mozillazine.org/Profile_Manager ) and see whether Firefox performs better then.

BTW: NS_ERROR_FILE_TOO_BIG doesn't refer to sessionstore.js itself being to big, but to the files sessionstore-1.js up to sessionstore-9999.js existing.

Comment 4

[David Lieber]

No files ending in .moztmp or any hypen files.  FYI - NSSessionStore no longer exists at all as I was requested to delete it.  But Firefox has not automatically created a new file with this name?

Instead of deleting profiles, I started Firefox in safe mode.  No differrence in behavior.

Comment 5

[Simon Bünzli]

Oh, you deleted the wrong file. It's not nsSessionStore.js (note the leading ns) but just sessionstore.js - and the file is found in your profile folder <http://kb.mozillazine.org/Profile_folder_-_Firefox>, not(!) in Firefox's installation folder. Please reinstall Firefox 2.0.0.6 (to resurrect nsSessionStore.js which is required and not automatically regenerated at all) and try again...

(In reply to comment #4)
> Instead of deleting profiles, I started Firefox in safe mode.

No need to delete a profile, but if needed just create a new one - there are a few differences between a new profile and safe-mode which could be relevant. But please try the other steps as outlined by comment #3 first!

Comment 6

[David Lieber]

Firefox team..thank you.

I removed all 9,999 SessionStore files; all 5464 cookie files; and 246 localstore files and 10 pref files.  Firefox flying again.

Any reason Firefox isn't cleaning up itself and keeps creating these phantom files. Should these bug change to address that issue or is it a known issue already.  FYI - all above files listed were zero byte files.  

Thanks again.

Comment 7

[Simon Bünzli]

Firefox shouldn't create any more unwanted files as of version 2.0.0.5. Should you ever see them again with the latest version, please file a new bug.