View Full Version : "applet" High CPU Usage

03-14-2008, 11:03 AM
Is anybody else experiencing this problem? This is on a dual 1.8 G5 with a scheduled nightly copy job. The "applet" process hovers around 100% CPU usage, with that load switching occasionally between the two CPUs. Inspecting the process, it is Copy Job.app/Contents/MacOS/applet from inside the .sdsp file representing the scheduled copy job. Killing the process of course resolves the problem, but presumably leaves me without a scheduled job. Even after rebooting the system, after everything is loaded up I'm left with this high-CPU process.

Any ideas?

03-14-2008, 12:19 PM
After rebooting? From what we can tell, this only happens if you've scheduled a backup and you aren't logged in when the schedule fires...

04-07-2008, 10:15 AM
I'm having this issue as well - OS X 10.5.2 Server, 1.8Ghz G5 iMac.

Is there any way to avoid the applet CPU usage bug when someone isn't logged in? For people with OS X Server, it's common for nobody to be logged into the console.

FYI, I'm in the Apple Consultants Network and I frequently recommend SuperDuper - by my recommendation, dozens of copies of SuperDuper have been sold.

04-07-2008, 10:29 AM
We're investigating the problem: this is new behavior on Leopard, quite unexpected, and also a bug, since we never even get a chance to fail -- instead, the script driver is 'hanging' before our own code in there even runs.

04-09-2008, 04:27 PM
Glad to see this is being treated as a known bug. It has been an ongoing problem on several of my installations since the Leopard version came out. Any idea on an ETA? It's a rather annoying problem, as my users often tell me their computers are running slowly and it's usually a result of this.

04-09-2008, 06:03 PM
We basically never provide ETAs, sorry, but a fix is due in the next update.

12-25-2008, 11:02 AM
I noticed this as a problem (fan running like crazy overnight - process "applet" using 99% CPU)
Is this not resolved? Downloaded SuperDuper again and it appears to be same version I got in Feb 08 (2.5 v84)

12-25-2008, 02:39 PM
It's resolved in the next update. Until then, the issue is as described: if you're logged out when the schedule runs, this can happen. You can quit "applet" in Activity Monitor...

01-02-2009, 01:56 PM
Thanks. I think you meant to quit "applet", not "Apple." :)

01-02-2009, 01:58 PM
Indeed; fixed.