How to Fix, iCloud.exe using more than 1GB RAM memory?

crashnburn

macrumors 6502
Original poster
Nov 18, 2009
338
13
How to Fix, iCloud.exe using more than 1GB RAM memory?


[1]: http://i.stack.imgur.com/oBFWv.png


I noticed it few days back after I installed/ upgraded latest iCloud setup after upgrading to iTunes 12.3.0.4 to go to iOS 9.x.

Figured it was a freak incident, so after the last sync yesterday night I left it on without any activity where it was aroun 500 MB or so.

This morning it had leaked to 1GB + again.

Something is way off. How to fix it?
 

crashnburn

macrumors 6502
Original poster
Nov 18, 2009
338
13
This is happening back in September since iOS9 release and wasn't fixed with iCloud 5.0.

https://discussions.apple.com/message/29036609
Read thru it all.. I just noticed it now, where apparently people have been facing it for a while?

1.2 GB memory for no reason, noticed first at 400/ 500 M and then just grows by itself even when machine is idle.

Win 8.1 x 64 Pro.

I had just upped to iTunes 12.3.0.4 / 12.3.1 for iOS 9 Update. It suggested to install the latest iCloud setup.. which I did, big mistake and then Started happening after.

I am wondering if we should uninstall iCloud.exe and reinstall the last older version that was not leaking on my PC.
 

thed0g

macrumors regular
Oct 22, 2015
176
205
The software has nothing to do with it, since the previous version (4.1) was released in July 2015 and was working fine until September 2015. Personally I noticed the memory leak somewhere around the iOS9 release when my iCloud storage was upgraded when I updated the phone, so I logically combined that would be the cause. That was still the time with previous iTunes (12.2) and iCloud (4.1) software, so those aren't the problem.

But since another user noticed the same while using iOS8 and never upgrading their iCloud storage, I'm not sure if this is the case. If the issue is on Apples backend and the iCloud client speaking to it uses more and more memory, then the only fix is for the Apple to change something on their end / or update the client to prevent this from happening.