Enough! What to do about browser piggishness

All browsers greedily suck up processor and RAM resources, slowing and even stalling PCs

I've finally had it! I've lived with this problem for so long now that I started to believe it always existed and nothing could be done. My system, a dual-core, 4GB monster of a machine, slows down to a crawl. I bring up the Windows Task Manager only to find that my browser is at fault. I use both Firefox and Internet Explorer, and they are both offenders, though Firefox is the one that seems to hog the most: slowly grabbing processor and memory resources until my work stalls. I then must stop the process and recover the browser so that I can begin again. Sound familiar?

There are all sorts of theories on which browser is better or faster, and depending on whom you trust, you will find a different winner. I personally don't care about the performance of each when I start the browser. After all, no matter which I choose, I end up in the same place: My browsing and computing experience slow to a crawl.

[ Read the InfoWorld Test Center's head-on comparson: "IE8 vs. Firefox 3.5: The browser wars continue." | See why InfoWorld's Randall C. Kennedy says Firefox is doomed. ]

It doesn't seem to matter which method of RAM use a browser has. IE7 and Firefox both use a single process that hosts multiple tabs (as many as you can load up before it cracks under pressure). Chrome and IE8 use multiple processes (which take up more RAM than Firefox). But Firefox eats up your RAM over time by just sitting there. You can watch it rise and rise. I decided to find the solution -- and found none.

In my quest to eliminate the problem, I've come upon the following solutions -- none of which truly satisfies me:

  • Switch to a different browser. Which one? Internet Explorer 7/8, Firefox, Safari, Chrome -- they all perform poorly (although some worse than others) if the same amount of pressure is applied. After experiencing a Firefox crash, switching to Chrome or IE seems faster, but only because you had 50 tabs running in Firefox when it finally collapsed, and only a few in Chrome or IE when you switched in frustration. But if you put the same pressure on any of the browsers, you'll find that they all disappoint to some degree on processor and memory hoggishness.
1 2 3 Page 1