Q: Memory leak on W7 x64 Post iOS9 upgrades iCloudServices.exe

I posted a workaround for this problem a few posts back up here.

Re: Re: Memory leak on W7 x64 Post iOS9 upgrades iCloudServices.exe

It's working very well and keeps all the icloudservices active. The highest memory use I've seen comes to around 120 MB during the hour or in between hourly restarts, depending on when Outlook restarts it during the hourly interval.

Thanks for the information.  Since my last posting the working size of icloudservices has grown to over 100 MB I've seen it grow 300 MB.  I'll try your workaround.

Hi Philip,

There are a couple of issues I have with the workaround proposed:

1. I am not in a position to understand what this executable does, how or how often. Force terminating iCloudSerives.exe while it is doing what it does has risks associated with it. Until Apple are able to confirm that killing the process at regular intervals, as per your solution, is not likely to cause damaged or lost data, I'm steering clear of it.

2. Apple should simply fix the memory leak. They're the richest tech company on the planet. The problems is consistent and 100% replicable. It couldn't be much easier for them.

Cheers,

David.

Hi David,

Yes, agree that I can't be 100% certain that a synchronisation process that is under way just when the process is being killed won't be affected by a forced kill of the icloud services. So far though, I've not had any issues... Outlook maintains a TSR copy of it, so it continues to function even though it has been killed off. What you will see though, is that the Outlook system tray icon disappears, therefore not allowing you to access the iCloud Services control panel. If you need it though, you can at any time just simply load it via the Program Files.

I hope that your ticket will have greater success than those raised earlier by some other people, going back now to September last year (after iOS 9 was released).

I do need the sync running between my PC and iOS devices, so have no option but to continue to run iCloudServices. Let's hope that Apple get the message this time and get on with it.

Phil.

Hi David,

Have you received an update from Apple yet as to when they're likely to begin looking at the problem? So far btw, all is running as expected wrt to syncing with the workaround I posted (and have now been running for the last few weeks) and no loss of any data.

Woah. Apple clearly do not care about this memory leak. Perhaps we should alert the tech press and see if someone will cover it?

Same here. 860K 38-40% CPU. Have killed the process and computer returns to normal. This has been ongoing now for 12 months. Win 7 Home Premium x64.

Anyone tested iCloud version 5.2?

I have been running 5.2 for the last week. It seems to be much better than the previous version but the memory leak is not completely fixed. The memory size is increasing by about 200Mb per day. At least now, you can't see the memory size ticking upwards while you watch in task manager.

I have been running iCloud on a Win7 x64 for a few years with no memory problems.  I now have a memory leak after upgrading to 5.2 a few months ago.  Memory usage climbs about 250MB every 24 hours until computer is crippled.  I have been restarting to fix it.  Major pain.