Simple solution don’t use FireFox

The very same problem exists for KomodoIDE, a software development tool that is based on the FireFox code and the solution there seems to be the same: “use a smaller project that has less files”.

If the internet connectiosns are fast enough, the disk based caching does not matter, as long as the memory based caching is switched in. So, my suggestion: allow the FireFox to use generous amounts of RAM, but disable disk cache.

Instructions:
1) type “about:config” to the address bar (the place, where URL-s are usually written), but without the quotes.
2) type “disk” to the searchline, but again, without the quotes
3) from there doubleclick on the line
browser.cache.disk.enable
so that it will be assigned the value of “false”.
4) Check that the setting modification actually worked for you by restarting FireFox and set the browser.cache.disk.enable back to “true”, if it didn’t, i.e. if the CPU burning problem persists.

It’s a crap browser – simple. I mean I like it more than Googles IDIOT minimalist set up – because I have landed on my head too many times and hate trying to guess at things I rarely use and are hidden; IE – that is just a bag of Microsoft forced vertical integration into everything else Microsoft, and Opera – that is a neandethal set up if ever there was one….

But when you go do a search on “Firefox is shit” and see the amount of sites that come up – and then compare your own experiences and the “Glowing Terms” that the people of the Mozilla foundation speak – of security, speed, stability etc…

Once you get past all the phases of the moon patch up jobs and bullshit – your going to come to the realisation that the core issue is that THIS browser it’s self, and the way that it is programmed; this is the core issue.

All this crap about broken profiles, javascript, flash, phases of the moon, frying the wrong side of the egg, aural cleansing, compatability with add on’s etc., etc., etc.. and of course the operating system issues – well I run Linux and this pus bag browser still bogs down to the roof…..

The only solution is to have a premeditated act of killing the damned thing off – set up and running in the background….

In Linux it’s Alt-F2, and the command XKILL, then place the RUN button to the right side of the slightly minimalised browser window.

I think the same thing can be set up for Windows, with Ctl + Alt + Del, and have “Kill Process” set up for Firefox, with only the “YES” left to click on before you shotgun this pus bag browser into oblivion.

Of course you could always come back to these forums and resort to waving magic beads, incantations, phases of the moon, astrological charts and putting the fist of Mars into the House of Uranus….

http://www.bukisa.com/articles/328432_100-cpu-how-to-fit-it-a-complete-troubleshooting-guide

*Here is a reference web site page for more on Javascript:

http://www.w3schools.com/js/js_intro.asp
Copyright 1999-2010 by Refsnes Data.

However, the second point (neglecting the confusion between java and JavaScript, or at least the text/image mismatch, which lead several people to miss the point), seemed quite thrilling to me, so I made a few tests. Here is the conclusion : unfortunately, the effect of disabling java is at the least completely negligible, even with a not so young computer. Actually I did not see any effect at all.

Concerning Andy’s suggestion in the comments, you can find more informations about the key he is referring to at http://kb.mozillazine.org/Browser.cache.disk.capacity but honestly I don’t think it should have a huge effect since it mainly affects the disk usage. I would rather consider the following key, which is not related to the CPU usage either but to the memory usage, which is also critical : http://kb.mozillazine.org/Browser.cache.memory.capacity

In what world are you living??? Most MAJOR sites now use javascript to manage DOM objects and create client side effects!!

The fix for Linux was to change the default value of the parameter Urlclassifier.updatecachemax from -1 to 104857600. The -1 value for the maximum cache size means unlimited and is the default value for all other operating systems while the value for Linux has been set to 104857600 which is 100 Megabyte.

Have a good day

BTW, has anyone else tried Andy’s advise successfully?

1. Open Firefox.
2. Type ‘about:config’ into the address line and hit Go or return. This takes you into the Firefox expert config menu.
3. See if there is an entry called browser.cache.disk.capacity.
* Yes? then modify the value to 16384, close Firefox and restart Firefox. It’s fixed.
* No? right click somewhere on the about:config page and select Integer. Create an Integer entry called ‘browser.cache.memory.capacity’ and set it to 16384. Close Firefox and restart Firefox.It’s fixed.
4. Check the CPU and memory size by ctrl-alt-delete and select the Performance tab… look for the firefox.exe process and the CPU for Firefox should now stay nominally under 10%.