I am running Leopard that I upgraded from Tiger.
I've been noticing that every once in a while the SyncServer process starts up and eats up all the CPU. The fans will start going at full blast and the laptop will slow down to a crawl. I need to force quit the process from Activity Monitor to get it under control. It disappears for a while, but eventually gets started again.
I do have an iphone as well that I sync so I'm wondering if syncServer might be an apple process checking for my phone plugged in.
Edit: Tried iSync and the manual resetsync as suggested, but got this output:
$ /System/Library/Frameworks/SyncServices.framework/Versions/A/Resources/resetsync.pl full
2010-03-12 08:03:50.230 perl[176:10b] SyncServer is unavailable: exception when connecting: connection timeout: did not receive reply
PerlObjCBridge: NSException raised while sending reallyResetSyncData to NSObject object
name: "ISyncServerUnavailableException"
reason: "Can't connect to the sync server: NSPortTimeoutException: connection timeout: did not receive reply ((null))"
userInfo: ""
location: "/System/Library/Frameworks/SyncServices.framework/Versions/A/Resources/resetsync.pl line 16"
**** PerlObjCBridge: dying due to NSException
And during that syncServer started spinning up 95-100% just like it always does.
Best Answer
You could try this :
Open iSync. Choose Preferences from the iSync menu. Click Reset Sync History. If this does not resolve your issue, or if you are unable to open iSync, follow these steps:
In the Finder, choose Utilities from the Go menu. Open Terminal. In the Terminal window that opens, type or paste the following command on a single line: /System/Library/Frameworks/SyncServices.framework/Versions/A/Resources/resetsync.pl full Press Return. When the operation is complete quit Terminal.
After you have reset the SyncServices folder, you may need to re-enable some Sync-related settings. Resetting SyncServices resets your Mac OS X User Account's Sync settings and any local history of updates and changes to Sync-enabled data. It won't change your current data sets, but it does delete the history of how the data arrived at its current state and disables some Sync-related settings.
Source