Hi everyone :)
Since upgrading to Leopard last week, I have spent most of my time trying to fix its effects.
One of them seems to be that Omniweb, even when supposedly inactive in the background, will suddenly hog the CPU. The only way to stop it is to Quit it, or ForceQuit it if it is particularly unresponsive.
I'm doing this several times an hour, which is excessive.
Console has no comment. There is no activity that I can find, which is puzzling.
Is anyone else experiencing this? I know CPU-hogging problems with Omniweb have been discussed before, but this is a sudden change following the Leopard update. Prior to the update, Omniweb was a good citizen on my MacBook.
Thanks for any help you can offer. :)
Since upgrading to Leopard last week, I have spent most of my time trying to fix its effects.
One of them seems to be that Omniweb, even when supposedly inactive in the background, will suddenly hog the CPU. The only way to stop it is to Quit it, or ForceQuit it if it is particularly unresponsive.
I'm doing this several times an hour, which is excessive.
Console has no comment. There is no activity that I can find, which is puzzling.
Is anyone else experiencing this? I know CPU-hogging problems with Omniweb have been discussed before, but this is a sudden change following the Leopard update. Prior to the update, Omniweb was a good citizen on my MacBook.
Thanks for any help you can offer. :)
Threaded Mode