0.7.4 CPU Load Extreme on OSX 10.8.2

[shypike]

What do you mean "after a download"?
During post-processing par2 and unrar will use significant CPU time.

[ApexDE]

I have the exact same problem as the OP when using the ML Build on ML. After a job is finished, including all par2 checks/repairs and unrar, CPU usage stays at 160-180% endlessly. This doesn't happen when i use the Lion Build on ML.

[shypike]

That's not what was happening on the OP's system at all.
It didn't happen after a download but during a download and the cause was determined and fixed in 0.7.6.
Is there anything in the queue when the CPU load goes up?

[ApexDE]

No, the queue is empty and sabnzb should be idleing, but CPU load stays at 160-180 % until i quit it and start it again. After another completed download the CPU load goes back to 160-180%.

[shypike]

When the queue is empty: stop SABnzbd and start it once like this:
Open a Terminal (Applicatiuons->Utilities).
Then type:
/Applications/SABnzbd.app/Contents/MacOS/SABnzbd --clean

[ApexDE]

Same thing, except that CPU Usage stays at exactly 100% after download is complete and post-processing is finshed.

[shypike]

Have you checked whether it is actually SABnzbd that uses so much CPU?
Under those circumstances, is SABnzbd's web interface still responding normally?
If it it really uses so much CPU, you would have to notice.

[ApexDE]

Sure, activity monitor shows 100% CPU Usage of sabnzb. the webinterface was a bit sloggy but worked. I just switched back to the Lion version and all is normal after a download. I'll stick with the Lion version. I wonder why nobody else has this problem on ML.

[shypike]

I wonder why nobody else has this problem on ML.

I wish I knew.
The total amount of factors is simply to large.
Could be anything, from simply a bug in SABnzbd to a bug in a driver, OS, security software etc.
Plus your specific setup and local network.
These things happen, it's statistically very improbable that SABnzbd would work on
every system it has been installed on.

Given that the Lion build doesn't exhibit the problem is interesting, but it does say very much either.
If you're in for some further experimentation, you could try the ML build again and
then switch off the ML-specific features. Those are Notification Center messages and standby-prevention.
The latter can be disabled in Config->Special, uncheck item "keep_awake".
Then restart.

[ApexDE]

I disabled keep-awake since it was introduced, as it kept my machine from being able to sleep. It simply stayed awake even if sabnzb didn't do anything. I'll give the notification option a last try

[shypike]

I disabled keep-awake since it was introduced, as it kept my machine from being able to sleep. It simply stayed awake even if sabnzb didn't do anything.

Interesting, my first reaction is to say that there's a causal relationship.
Not that the keep-awake code is the cause, it cannot be because you disabled it.
But it does point to SABnzbd thinking it has something to do.
The keep-awake code is active as long as there are active items in the queue (download or post-processing)
and the system isn't paused.
The 100% CPU suggest that the "empty detection" goes in an infinite loop.
Still a mystery why it doesn't happen with the Lion build.
I'll do some further digging, but don't hold your breath.
One more question: if, after download, the CPU goes to 100%, what happens if you add another NZB?

[ApexDE]

I noticed that the high cpu load starts even further, it starts by adding a nzb to the queue and it simply stays that high after finishing the job. Using Lion Version i have 40% cpu load when downloading, with the ML Version i have 150-180% while downloading and it stays that high after the dl job is done, until i quit SABNZB and relaunch it.

[shypike]

Getting more and more mysterious.
Are you using some kind of security suite on your system?
(We had an issue once with a security suite on Windows systems, which required a hotfix
from Microsoft to solve it.)