Logged out for schedule cause 'applet' to hog cpu
 

I have a problem where if I am not logged in when a schedule is due to run, the applet process hogs an entire core until I force quit it. I have since learnt that the backup will not happen while logged out, but I wouldn't have though it would cause a problem like this.

Below is what I see in Console at the time the schedule is due to run. (Edited)
Just wanted to bring it to your attention.

Thanks, yes - we're aware of the problem. (The core hogging is weird OSX behavior where they're locking us up before we get a chance to quit.)

We've worked around the new behavior in the next update.

That's good to know. Do you have a timeframe for when that update will be available to us?

Whenever I try to make a guess at that kind of thing I end up disappointing, so -- no. :)