-
All replies
-
Helpful answers
-
Nov 10, 2014 2:39 AM in response to mswampby Ruccula,Dear all, Thank you for this thread.
Obviously I have this problem too and been suffering from it greatly in my daily work. It got so bad I started using Postbox in the meantime (which is actually a very nice Mac Email program, I particularly enjoy the possibility for labels).
So, on my computer it became soon clear that the memory drain is worst when I was writing an Email, even worse, when there was an attachment attached!
I did like most, monitored with activity monitor and restarted when the RAM was too low.
I am using two iCloud Mail accounts, one POP and one IMAP GoDaddy.
And YES, unchecking "Store draft message on server" for the IMAP GoDaddy account DID remove the problem.
The second Mac in our house did have NO problem ever (it runs an iCloud Mail account and an Exchange one, NO Go Daddy account.)
I hope this adds to the data collection. Many thanks!
-
Nov 10, 2014 11:40 AM in response to emacinboundby Lfromny,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.

-
Nov 10, 2014 11:49 AM in response to Lfromnyby Doren_Sean_Michael,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 mswampby NewYorkMacOwner,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 3:40 PM in response to NewYorkMacOwnerby Lfromny,Thanks NewYorkMacOwner - I did call today but they were having issues. They want to screen share and their system wasn't allowing it so I have a case number and will call back tomorrow. I have tried the other suggestions here with no luck. Hopefully, Applecare will be able to resolve. If so, I will post, the solution if possible.
-
Nov 10, 2014 6:41 PM in response to Lfromnyby Doren_Sean_Michael,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:47 AM in response to BraxDadby bwbonnell,I am having the same issue with essentially identical computer setup. Today I had to reboot twice While trying to send out an email. Mail was the only program running. The computer runs fine if mail is not running. There are no 3rd party plug-ins. It all started since "upgrading" to Yosemite. Terribly frustrating!
-
Nov 11, 2014 4:53 AM in response to Doren_Sean_Michaelby Anil B.,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.
-
Nov 11, 2014 5:20 AM in response to Anil B.by etresoft,Anil B. wrote:
I am posting this so Apple will be aware that multiple users are having this issue.
Apple doesn't read these forums. The only way to make Apple aware of the scope of the problem is to file a bug report. Apple doesn't even read the bug reports, but they do count them.
-
Nov 11, 2014 5:36 AM in response to etresoftby Anil B.,You have to be an Apple Developer to file a bug report I believe.
-
Nov 11, 2014 5:39 AM in response to Anil B.by Paintbox,No. I filed one without being a developer. However, the reply I got was that the problem was already in the system.
-
Nov 11, 2014 5:43 AM in response to Anil B.by etresoft,Anil B. wrote:
You have to be an Apple Developer to file a bug report I believe.
You can sign up for a free developer account.
-
Nov 11, 2014 5:46 AM in response to Paintboxby etresoft,Paintbox wrote:
No. I filed one without being a developer. However, the reply I got was that the problem was already in the system.
Yes! That is what you want. That means your vote was counted.
-
Nov 11, 2014 11:15 AM in response to Anil B.by 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 mswampby Rob Hambly,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....
