The bloom is off the rose. The thrill is gone. I may be looking for a new browser.
If you have been using Firefox regularly as I have been, you had to sense that something was wrong. There were the crashes where I lost my profile. I know I'm not alone because my post on fixing the Firefox profile problem is hit constantly. I have found that certain sites don't load and others load slowly including Typepad. I wrote it all off as quirks of the program until I read Matthew McKenzie's piece on the Firefox memory leak at Linux Pipeline.
While my problem is not as severe as reported by McKenzie--he reports Firefox using up nearly 500 MB of RAM--I have been watching and I've found that Matt is not alone with this problem. I opened my Task Manager yesterday and found Firefox at well over 100,000 K of memory, and I could literally watch the memory usage climb steadily. I opened IE and found Internet Explorer around 34,000 K and that Opera with multiple tabs open at just over 31,000K and they weren't climbing steadily.
While I write this I have the Windows Task Manager open and I'm watching Firefox approach 100,000 K. I tried closing tabs to see if Firefox would give memory back and it didn't. As McKenzie writes, this is a *big* problem and the folks at Mozilla.org need to fix straight away.
If you want to check to see if Firefox is eating your RAM, do the following:
- Open Firefox.
- Open the Windows Task Manager by pressing Ctrl-Alt-Del simultaneously.
- Click the Processes tab.
- Click the Image Name column to sort alphabetically by image name then check the entry for Firefox entry and watch the Mem Usage column.
If you are finding a similar problem, leave a comment and let me know.