About Me I am a MacUpdate Desktop user
Gender: Male
FileMaker Pro database development FSA member. ATSOffice database software packages. Audio, video, audiovisual design, consulting programming; CEDIA certified designer/programming of home theater & home automation systems.
Visit Stats
Last Visit: 4 years ago
Member Since: 29 Dec 2006
Profile Views: 175
I tried this new version and it exhibits the same traits of the old ones in terms of memory and CPU time. The worst part is the daemon that consistently takes up 100% of one of my four cores of processors and sometimes much of the others on a MacPro, even when my computer is not in use. Until this is fixed I cannot afford to devote that much CPU time to something that is supposed to be just tracking software installs.
I went further with the CPU hog issue by monitoring CleanApp in the Apple Activity Monitor deeper to see its behavior over time. When I first noticed it hogging the CPU (at the time was 100% of one core) it remained at that level for more than 30 minutes when I finally just quit the daemon.
While the explanation that it is waiting for idle time to do its work may be a noble thought, taking this much time to simply log events is far, far too consuming of CPU time is out of proportion with the task, unless is it writing a novel. Something is still wrong and the developer needs to fix/improve that aspect of the program.
If your computer is asleep, you have to use the Power Management feature to have your computer wake up a few minutes before an alarm for it to work. This is a real hassle, so I am using Awaken instead. I like the extra features it has over Awaken, but having to set and coordinate two time settings is a huge inconvenience so I will not use it as it is.
[Version 8.2.8]
There are currently no troubleshooting comments by this member.
Please login or create a new MacUpdate Member account to use this feature
CleanApp
+1
While the explanation that it is waiting for idle time to do its work may be a noble thought, taking this much time to simply log events is far, far too consuming of CPU time is out of proportion with the task, unless is it writing a novel. Something is still wrong and the developer needs to fix/improve that aspect of the program.
+1
Alarm Clock Pro