Page 1 of 1

AppleSyncNotifier using 50% CPU after resume

Posted: Mon Jan 25, 2010 11:42 am
by VietNinjaXTC
I'm using Apple's push sync service (MobileMe) which requires a client software be installed. The service associated with the program is AppleSyncNotifier.exe. The problem I'm having is that this process is eating up 50% CPU (according to the task manager) whenever the laptop resumes from a standby state (sleep or hibernate). This wouldn't be such an issue if I had a quad-core Mac, but on an ultraportable laptop, battery life takes a serious hit when the CPU is running that hard constantly.

Right now I have to go in an kill that process (which then eliminates syncing between my laptop and my phone/web server) as the only way to remedy this problem. Is anyone else experiencing this? Any fixes?

My setup:
X61 Tablet
Windows 7 Enterprise
160GB HDD
4GB RAM (physical)
Intel L7500 (1.6Ghz)
Office 2010 Beta (which the software is to sync with Outlook)
Latest MobileMe client software (downloaded and installed 01/24/2010)
No updates found for iTunes (currently 9.0.2)

Thanks!
Jeff

Re: AppleSyncNotifier using 50% CPU after resume

Posted: Mon Jan 25, 2010 12:28 pm
by ThinkRob
VietNinjaXTC wrote: Right now I have to go in an kill that process (which then eliminates syncing between my laptop and my phone/web server) as the only way to remedy this problem. Is anyone else experiencing this? Any fixes?
I'd check over at Apple's support forums/KB.

I'm almost 100% positive this isn't related to your hardware in any way -- it just sounds like a buggy piece of software.

Re: AppleSyncNotifier using 50% CPU after resume

Posted: Thu Jun 03, 2010 11:21 am
by rwangxun
Another very old post. But if you want to know how I have worked-around this problem, check my post here on Lenovo's forum:

http://forums.lenovo.com/t5/X-Series-Ta ... 7165#M8625

Hope this would help! :D

Re: AppleSyncNotifier using 50% CPU after resume

Posted: Thu Jun 17, 2010 6:07 am
by rwangxun
MobileMe Control Panel upgraded to 1.6 yesterday, but still no luck. I have to implant this work-around for some more time... :?