[Stormchild]

Originally Posted by JKT

From what I have seen in other threads from OmniGroup personnel, this is linked to Javascript and/or garbage collection (whatever that is).

Garbage collection is an automated process of cleaning out bits of data that are stored in memory when a program runs. This helps avoid accumulating memory usage by getting rid of things that are no longer needed. In JavaScript itself, you don't do any memory management, which means it's the responsibility of the runtime engine (the program that interprets and executes your JS code; in the case of OW, this is provided by WebKit afaik) to handle memory management, including garbage collection.

Accumulating garbage (unused data in memory) shouldn't have anything to do with CPU usage, but the garbage collection process very well might.

[Ward]

When I visited the beta download page in response to OmniWeb's automatic notice of the new release, I noticed this:

"Known issues in OmniWeb -- Plug-in Content will continue to play in inactive workspaces."

This seems a likely explanation for the constant CPU activity that prompted my opening this thread.