MacDroidNotifier consuming 50% CPU in getattr calls

[GoogleCodeExporter]

Some users are reporting that MacDroidNotifier is consuming about 50% of 
the CPU in calls to getattr.

I suspect this is related to login items - we watch the login items for changes 
and re-read it whenever it's changed. If that's the issue, my initial proposal 
is 
to stop listening on the changes and instead just read it every time 
preferences is opened, possibly then posting the update to the bindings. The 
downside of the solution is that, if the app is added to or removed from the 
login items while preferences is open, the change will not be shown 
immediately.

Original issue reported on code.google.com by rdamazio@gmail.com on 25 Jan 2010 at 5:50

[GoogleCodeExporter]

Missing Sync for Blackberry was causing this problem for me.

After removing it from login items and rebooting, I no longer have this 
problem. 
Interestingly enough, it isn't sufficient to kill all the Missing Sync 
processes. 
Apparently some sort of event trigger set up by Missing Sync lives on even 
after the
processes are dead.

Original comment by satw...@disjoint.net on 28 Jan 2010 at 7:17

[GoogleCodeExporter]

r66 fixes this. Thanks again for the detailed feedback.

Original comment by rdamazio@gmail.com on 28 Jan 2010 at 3:36

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by rdamazio@gmail.com on 7 Apr 2010 at 6:03

• Changed state: Released