Right. I meant that maybe the reason I wasn't seeing it eat CPU was that it just wasn't working for me.
I haven't restarted the browser in a good while (most of a week).
That could be it, then. 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.)
Actually, memory leaks could explain the CPU usage: garbage collection can be extremely CPU-intensive in pathological cases—e.g., when JavaScript is repeatedly polling the chat server, constructing and discarding objects representing the connections.
Re: Huh
Right. I meant that maybe the reason I wasn't seeing it eat CPU was that it just wasn't working for me.
That could be it, then. 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.)
Actually, memory leaks could explain the CPU usage: garbage collection can be extremely CPU-intensive in pathological cases—e.g., when JavaScript is repeatedly polling the chat server, constructing and discarding objects representing the connections.