Yosemite OS 10.10 Mail Memory Leak

Since upgrading to Yosemite I have ran out of memory (MacMini, 16 Gbytes) three or four times. I have traced this to Mail.app. The trigger seems to be when you drag multiple files into the email to have them included. Then, the memory usage starts racing, eventually using up all free memory within seconds. The only way to recover is to use Force Quit from the Activity Monitor, normal Quit from within Mail does not work. See the attached screenshot. By the time I grabbed the screen shot and pressed Force Quit, it was already up to 17 Gbytes of Memory.


Has anyone else came across this problem?


User uploaded file

iPad 2

Posted on Oct 19, 2014 5:17 PM

Reply
326 replies

Nov 10, 2014 11:40 AM in response to emacinbound

I have been having the same basic problem, however, not with attachments. I will be writing a basic email and get an error that I am out of appication memory. After looking in the forums for info, I took a screen shot of memory usage and found that Mail is taking almost 60G of memory when this occurs for no particular reason. I do usually have several applications open but this is definitely a memory issue related to mail. Rebooting does not help except rarely. I am thinking of going back to mavericks. I am on a macbook pro 13" 3GHz Intel Core i7, 8 GB 1600 MHz DDR3.User uploaded file

Nov 10, 2014 11:49 AM in response to Lfromny

Hi, Lfrommy, I understand that this is a long Discussion but several temporarily solutions are listed throughout that might help you. I suggest you actually take the time to read through this Discussion and respect the time and effect the other Users have taken to post their advice. None of these "solutions" have been marked as solving the issue per se, because, technically, they don't. This is still an issue that Apple needs to address prior to their next update. Thank you.

Nov 10, 2014 3:27 PM in response to mswamp

I wish I could tell you precisely what we did to rectify the problem for me, but I'm afraid it's all a blur. That said, Apple did NOT charge me for tech time on the phone since this was a problem caused by the update. After about 40 minutes, voila, my system is back to normal with Yosemite running and without any memory loss issues or lagging. Worth the phone call and the time spent on it.

Nov 10, 2014 6:41 PM in response to Lfromny

Wow, this is incredible because when I called 2 weeks ago they had no clue how to fix it and said that the next tier of tech support and a senior representative would call me back and I'm still waiting. I can't wait to hear what they did. I sure hope they didn't simply turn off Drafts like was my temp solution because this is not a fix and that would be totally unacceptable. We're all waiting very patiently I suppose for your next post. Thank you!!!

Nov 11, 2014 4:53 AM in response to Doren_Sean_Michael

I truly regret updating my MBP mid 2010 8GB system to Yosemite.


I also have this memory leak, Mail related issue on my MBP. I had it on my iMac mid 2007 which I reverted back to Mavericks with a clean install.


I don't want to do same thing on the MBP. I am posting this so Apple will be aware that multiple users are having this issue. Mail is the offender. See attached screen capture.


User uploaded file

Nov 11, 2014 11:15 AM in response to Anil B.

I just replicated this problem where the memory hog was Time Machine backup process. Upon clean reboot, I didn't launch Mail. After a few minutes, free memory started plummeting. It was the backup process, which took up 5 to 6 gb. My system slowed down, beach ball everywhere, typing was delayed. I stopped the backup, and boom, 5GB freed up and everything returned to normal.


What is weird is that I did not have these issues until yesterday. I installed Yosemite when it was first released and so it has been working fine until now.

Nov 12, 2014 2:37 PM in response to mswamp

So I just received a call from 916-399-7992 claiming it was an Apple Senior Advisor, who had been told by an Apple Engineer to call me regarding this issue (I replied earlier in the thread).. He wanted to get hold of some log files. After googling the number, I totally called him on on being a scam man.... told him to send me an email from his Apple account... and he did... Well slap me in the face with a wet fish....


Did I just call out David J from Apple as a scam artist! Ha... I should call him back to apologize... but I won't....

Nov 12, 2014 6:09 PM in response to Rob Hambly

A Senior Advisor contacted me also and I missed the call but he left a VM and I immediately called him back. They're asking for our help to simply save & send them a log file if we can replicate the issue again. This is how problems are solved. I think it's pretty ignorant that you're not willing to help. Everybody that has been posting in this Discussion has been willing to help you but when you're asked for help to solve the issue your response is "but I won't". Seriously? Have the decency to simply call them back. We'd all like this issue fixed and if it takes a few extra minutes out of my day to provide some vital information than I will do whatever I can. He also shared with me that when an issue escalates past a certain point on these Discussions that Apple does take notice whether if it's by considerable unique user posts, number of posts, etc... It doesn't really matter how, but that they do if it becomes a large scale issue which I think is incredibly respectful to their customers. My friends all say I should work for Apple as much as I praise them, but honestly, when was the last time you had any company go above & beyond to help solve your issue? And for free? Thanks.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Yosemite OS 10.10 Mail Memory Leak

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.