Ever since I installed Firefox 1.5 (and later 1.5.0.1) I have had nothing but grief. Freezes. CPU spikes usually in the 50s — which meant it took 20 seconds for anything to happen — but sometimes much higher, verging on 100%, which meant nothing happened however long I waited. Even if I didn’t get a CPU spike, going away from the machine with Firefox open in a window, even in the background, would make it freeze up, requiring that I use the task manager to kill it.
The problem was especially bad when I loaded a particular large and complex web page that I use several times a day (no, not this blog) — not only did it load slowly, but it would bring Firefox to its knees every time. And yet it worked fine in 1.07.
My first Google search suggested it was probably a plugin issue. I duly changed from Adblock to Adblock plus. I used less aggressive Adblock settlings. I replaced my tab manager with something that had a better reputation for playing nice with others. I removed this plugin, then that one. (See below for a list of what I’m running now — an only partly restored list from what I used to use.)
Nothing worked.
I disabled the prefetch. I turned off Bfcache — the caching of recently viewed pages — losing the lightening back and forth which was one of the best reasons to upgrade.
And of course I followed the directions at InternetWeek to play with settings in about.config to reduce the cache. And I carefully followed the directions as to what settings to use in place of the defaults for the about:config setting in browser.cache.memory.capacity.
Nothing worked.
But at last I can report that I think I have found the magic bullet: Ignore the directions in the cookbook about setting browser.cache.memory.capacity to 15000 if you have up to 1 Gig of RAM, or maybe 32768 if you have a full gig. I have a full gig of RAM, and it’s not shared with my graphics card, and my problem only went away when I shrank browser.cache.memory.capacity to the absurdly small 8192.
That worked.