So, for the past couple weeks I noticed that after about 3 or 4 hours of usage, one of the programs I use on a regular basis was having Memory Leak issues. Normally I just shrug it off and continue about my merry way, because I have better things to do than to find the source of the issue.
Well, it started happening today. I could feel the usual slowness coming on so this time, I decided to see which one was having the issues.
Lo and behold, the culprit was none other than Firefox. Now, I’m not saying that this is a new issue but, didn’t they claim this as fixed in 3.0? Guess not…
With 6 tabs open, Firefox was using a good 350 Megabytes of RAM. … say what?
So, of course, to debug the issue, I killed a couple tabs in Firefox. And, of course, the RAM usage stayed the same.
So, I told Mike about it and that when Opera implements CSS3, I’ll be permenantly switching to that.
He suggested I try out Flock again, which is a browser I used a lot a year or two ago. I was hesitant because it’s base is Firefox 3.0, not 3.5. I tried it anyway, and to my amusement when I signed into Facebook. A bar on the side popped with my Account info and the Live Feed.
So, I thought, that’s pretty awesome! And then Mike suggested I try Twitter as well, and sure enough, I logged into Twitter and boom, another Tab in the sidebar with my Twitter info as well as my Twitter feed.
Then, I did the scalability test in Flock. I opened my same six tabs that I had in Firefox, and looked at the Task Manager.
With Facebook and Twitter open in the sidebar, as well as FFCC, my blog, my blog control panel, my private IBB Alpha board, vBulletin.com, and AdminAddict.net open in browser tabs, Flock used a grand total of 110 Megabytes of RAM. Less than 3x that of Firefox, and Firefox didn’t even have the Facebook and Twitter stuff.
Even now, I’ve closed all tabs except for my blog and blog control panel. And Flock is now using 95 MB to 100 MB of RAM.
So, yeah, I’ve switched to Flock. 
