[zottel]

Just to tell you: In the Webkit version OW uses at the moment, there is a JavaScript garbage collection issue. A garbage collection is a part of the engine of a scripting language like JavaScript that looks at all the presently used variables and at all the memory that has been claimed to see which parts of the memory aren't used anymore in order to free them.

This doesn't work as it should, so the CPU usage goes to high values, and the memory isn't freed as it should be.

I'm not sure if this is the case for the older version of WebKit Safari uses, but it is for the current OW - not for Firefox or Camino, though, as they use a different rendering engine. So, if you regularly use heavy JavaScripting sites, for OW and maybe Safari you _might_ know the cause. This will hopefully be solved in future versions. For the other browsers I can't help you (and have never experienced the described behavior, but as I rarely use them at all, this doesn't mean anything).