Q: Yosemite OS 10.10 Mail Memory Leak

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.

Simmer down old chap... 

They will get their log files...  I was simply pointing out that it's legit and it took me by surprise...  and that I wouldn't call back 'to apologize'... Thanks.

Thanks Rob. I've simmered down. LOL Just had an emotional day and I think some of that spilled over to here. I apologize and thanks for sending your logs

Apple representative contacted me as well, both with phone call and email.  Email address was with apple, phone number caller ID was apple number.  I called an apple main number to be certain and used his extension and was legit.

Spoke at length with them on phone, so impressed by the effort.  Especially since it was a proactive gesture on their part and unsolicited since I personally never filed a ticket or anything.

Duplicated the problem for them in minutes, sent them multiple Diagnostic readings during Mail Memory Dump... and hoping this will help them resolve.

Also, my biggest issue is not the memory dump with GoDaddy IMAP which is easily worked around by disabling the draft sync... but instead with Apple Mail's inability to properly and consistently sync with new incoming mail.  Workarounds for this are more of a pain and limiting, requires quitting mail, taking offline and back on, etc.  And this isn't just a Yosemite issue, this issue persists from previous operating systems and versions of Mail.  Trying to see if I can get them to help resolve this as well.

I, too, received a call from an Apple "Senior Advisor" who seemed very interested in getting details.  He also asked me to run sysdiagnose if the problem surfaced and I offered to re-enable "Save draft messages on the server."  Within a couple of hours, I was in trouble, again, with only about 16MB of RAM.  I tried running the command he emailed me, but most of the steps timed out, I assuming due to limited system resources.  I'm still trying to get the resulting file to him, as it's over 14MB and too large to email.

I also did some screenshots to better convey what I was seeing and have already sent those to him.

The good news is that it appears that Apple has taken notice of this issue.  The bad news is that if they've already seeded 10.10.1, it may be too late for the next update?  Let's hope not.

Hi CTM, I had asked the Advisor about this possible scenario and asked him a question. Can I keep my Activity Monitor app open to monitor the Mail app's memory and when it begins can I activate the Command Line And then quit Mail? He said, yes, they only need the Log file to record a few seconds of the issue. This way we won't lock-up our entire systems and have to reboot but the only caveat is that you'd have to stare at your Mail.app for a few minutes till the issue started. I hope that makes sense. Thanks!

Happens here as well. NO plugins or third party stuff in Mail. No Gmail. One IMAP provider. One iCloud. Moved a mail message from Inbox to a folder. Consumed 24 GB of memory before I killed it.

Hi CTM just a note if I can be of help. When you said I'm still trying to get the resulting file to him, as it's over 14MB and too large to email.

You can send the file by using www.wetransfer.com a free file transfer service.  You can send up to 2GB of files free of charge.

Yes, exactly, there a quite a few free reliable and secure large email attachment services. Just be wise in which one you use. WeTransfer.com is great and we also sometimes use TransferBigFiles.com - Also remember of you have an iCloud Drive you can put it in there and email the Advisor the shared link. This is what I'll be doing because I know the file will be too large for an attachment. Thanks!

@wal073 -- thanks!  As it turns out, they sent me a link for uploading files.  It really seems like they're trying to help.

Ah, yes, that's correct, I had totally forgotten that they also offered that to me as well. Cool!

wal073 wrote:

 

Hi CTM just a note if I can be of help. When you said I'm still trying to get the resulting file to him, as it's over 14MB and too large to email.

 

You can send the file by using www.wetransfer.com a free file transfer service.  You can send up to 2GB of files free of charge.

Isn't this a Yosemite Mail thread? I thought Yosemite was supposed to support large e-mail attachments with Mail Drop. Are you suggesting that Yosemite e-mail is buggy?

Hi Etresoft.  I know Yosemite supports large email attachments but bearing in mind the problem the Mail app has of swallowing up memory I took it for granted he is not using the Mail app thats why i suggested to use wetransfer.  If Mail was performing well of course i won't suggest to use wetransfer but this is not the case: Mail is totally useless with 10.10 so to send large files you have to use a file transfer service

Ironically, I asked the Apple advisor if I could use that feature of Mail and he indicated he had not yet tried it.  They have a standard facility for accepting large files, so we simply chose to go that route to eliminate additional issues.

Exactly. It's impossible to email anything let alone large files with the Mail.app with this current issue. That was the only reason I was suggesting too because MailDrop would work perfectly for this under normal circumstances. Thanks!