If it's FF2, that could definitely be it; I try to keep mine open indefinitely, but I always have to restart sooner or later, what with memory leaks and all. (3.0 is supposed to have fixed most of those.)
Yaas -- probably the biggest reason I'm looking forward to 3.0. I run a lot of Google apps (email, calendar, reader, etc), so my memory usage tends to be pretty bad. I've been controlling that lately by not running quite as much at once (three windows at a time with half-a-dozen tabs total, instead of seven windows with 20-some), but I do wonder if the cumulative memory leakage is somehow interacting badly with Facebook.
I still suspect Facebook Chat is complicit (it's the only thing on the FB homepage that *should* be using a non-trivial amount of CPU); as you say, that sort of communication can be expensive, especially if the implementation is a little naive. Now I'm wondering what their protocol is, and what I can learn from it. CommYou is going to have some automatic polling, at least by default, and it would be good to not have similar problems...
Re: Huh
Yaas -- probably the biggest reason I'm looking forward to 3.0. I run a lot of Google apps (email, calendar, reader, etc), so my memory usage tends to be pretty bad. I've been controlling that lately by not running quite as much at once (three windows at a time with half-a-dozen tabs total, instead of seven windows with 20-some), but I do wonder if the cumulative memory leakage is somehow interacting badly with Facebook.
I still suspect Facebook Chat is complicit (it's the only thing on the FB homepage that *should* be using a non-trivial amount of CPU); as you say, that sort of communication can be expensive, especially if the implementation is a little naive. Now I'm wondering what their protocol is, and what I can learn from it. CommYou is going to have some automatic polling, at least by default, and it would be good to not have similar problems...