Thanks. Killing metacity helped return CPU load to normal.
However, there seems to be more to this bug.
You see, I always start compiz with the --replace parameter. Until a few days/weeks ago (I seldom restart) this worked fine. But since sometime in the Karmic development cycle, metacity unexpectedly keeps running in the background, eating lots of CPU cycles.
I can reliably start a Gnome session with metacity, run compiz --replace and have it result in high CPU load until I then do a killall metacity.
Thanks. Killing metacity helped return CPU load to normal.
However, there seems to be more to this bug.
You see, I always start compiz with the --replace parameter. Until a few days/weeks ago (I seldom restart) this worked fine. But since sometime in the Karmic development cycle, metacity unexpectedly keeps running in the background, eating lots of CPU cycles.
I can reliably start a Gnome session with metacity, run compiz --replace and have it result in high CPU load until I then do a killall metacity.