10.5.3 SyncServer Memory Leak

CG Rescue Swimmer,

You may benefit from from following the procedurs listed in: Mac OS X 10.5: Resetting the SyncServices folder.

Thanks for your service.

;~)

Glad to hear that procedure worked for you.

;~)

I am having the same issue. CPU is at 80-90%, 300MB+ being utilized and the heat is crazy. fans blowing up a storm. Genius bar couldn't help me. Found this and hoping it will help but ran into the same snag - ISync is freezing upon opening for me as well.

Can you tell me how you executed the terminal command? I am new to Macs, so a little nervous about mucking about in the system...

would really appreciate the assist.

Loving my new Mac aside from this little issue and I'm a long time PC user who may never go back.

Okay, so apparently in my distress over mucking up the inner workings of my mac, i stopped reading on the page recommended above in Mac OS X 10.5: Resetting the SyncServices folder. 🙂

In the second half it describes the terminal, etc. I cannot believe how easy that was! I mean, I did not have to know all of DOS to make it work. Thanks Ferd II and CG Rescue Swimmer. Glad I found this thread. so far just changing the terminal with the code you provided, Ferd II seems to have done the trick. Syncserver immediately dropped to almost nothing in % or MB.

I'm now having this issue, after sending the terminal command : and yes, it's still sucking all my resources.

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/resetsy nc.pl line 9"
** PerlObjCBridge: dying due to NSException

Ok, I was able to force quit the process "syncserver" using Activity Monitor, when I did that, I was able to execute the command, restart, and all fixed..

Once again, thanks! Wish Mobile Me support could have provided me with this fix, seems I spent the last three days working on this for no reason.

Cheers!

The first part of the solution didn't work since the "Reset Sync Services" button was grayed out. The second part worked for me though. Thanks!!!

Worked for the memory leak, but now my mobileme will not sync. I have done quite a few thing to resolve this (reset sync data, signed out and tried syncing with another account, which worked fine, signed back in using the mobileme account I was using then, rebooted, tried to resync, cleared keychain re-tried everything) I am at a loss of what to do now. Any suggestions??? Thanks

I am getting the exact same error. See screenshot:

http://hisnameistimmy.com/temp/syncserver-issue/screenshot3.png