MacUpdate: george26's Profile

User "george26" Profile

About George

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.

Real Name:George Wilkinson

Homepage:http://www.atssupport.com/wordpress

Email:

Last Login:9 Mar 2008 16:12

Posts:2

Recent Downloads:

(none)

User Reviews

CleanApp	Feb 4 2008	GEORGE26 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. (Version 3.0b1)		0
		[ 3 Replies - Reply ]

Replies:

CleanApp

Feb 5 2008

ANDREW SCOTT I've been finding exactly the same problem with the current beta version. It's very annoying to hear the fans of my MacBook Pro go into overdrive and find out the CleanApp daemon is grabbing 98% of the CPU for no good reason.
(Version 3.0b1)

CleanApp

Feb 6 2008

JEEPEE If you open CleanApp, you will see what's being logged at that moment. The developer told me that the CleanApp Daemon waits until there's enough CPU left for it to write things on disk. It also waits until an application or installer is ready with writing things to disk and when it's ready, the Daemon starts writing its log.

It seems that CleanApp will have to ignore some processes in the future, just to be sure it doesn't log unnecessary things.

If you have suggestions or questions, do write to the developer, so he can make CleanApp better.
(Version 3.0b1)

CleanApp

Feb 13 2008

GEORGE26 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.
(Version 3.0b2)

Alarm Clock Pro	Jan 26 2008	GEORGE26 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)		+1
		[ Reply ]

The opinions expressed in the reviews are not necessarily those of MacUpdate.
MacUpdate waives any legal binding related to the comments and opinions expressed in the reviews.
Please contact MacUpdate politely if you wish for a comment to be reviewed by MacUpdate for removal.