… and you’ve tried all the free-memory-on-minimize tricks out there, you could do a couple of things.
You could try to update to the newest version. If you’re using old extensions like I do, FireFox has already sent a bazillion of security alerts trying to talk you into the update process. Well, you’d get rid of the update alerts, but that doesn’t solve all your problems, because your beloved extensions were deactivated automatically.
A reinstall is brutal, but helps. Unfortunately you’ll lose a lot of stuff.
Waiting until your history.dat file exceeds 12 gigs and session saver forced the creation of prefs-9999.js in your profile is another way to handle the crisis. The prefs-9999.js is the ultimate prefs file, which stores all your settings by the way. Once FireFox creates it, it stops working all of a sudden and cannot be restarted.
I figured out that such a prefs-n.js file is created up to a few times daily, and with every new file FireFox slows down a bit. It is absolutely genial that in times of 64 bit integers the file counter has such a low hard limit. I mean I wouldn’t surf any more in a few weeks if my browser would become much slower.
So I appreciated the heart attack forcing me to look into the issue, deleted all prefs-*.js files but kept prefs.js itself, and now I’ve my fast FireFox1.5 back. I lost a few open tabs and such, because I was too lazy to rename prefs-9999.js to prefs-1.js. Memory allocation right after starting the browser went down to laughable 300 megs and still counting, so I guess there’s some work left when I want to continue surfing with hundreds of tabs in several project specific windows. Sigh.
I’m an old fart and tend to forget such things, hence I post it and next time my browser slows down I just ask you guys on Twitter what to do with it. Thanks in advance for your help.
Share/bookmark this: del.icio.us • Google • ma.gnolia • Mixx • Netscape • reddit • Sphinn • Squidoo • StumbleUpon • Yahoo MyWeb
Subscribe to Entries Comments All Comments