mswamp

Q: 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?

 

PastedGraphic-1.tiff

iPad 2

Posted on Oct 19, 2014 5:17 PM

Close

Q: Yosemite OS 10.10 Mail Memory Leak

  • All replies
  • Helpful answers

first Previous Page 9 of 22 last Next
  • by teonyc,

    teonyc teonyc Oct 25, 2014 8:05 AM in response to emacinbound
    Level 1 (0 points)
    Oct 25, 2014 8:05 AM in response to emacinbound

    Yes, have had the exact problem with my GoDaddy IMAP account both before and after upgrading to Yosemite. I've used the "sync mailbox" or quit and restarted Mail to resolve the problem.

  • by Steve Lidie,

    Steve Lidie Steve Lidie Oct 25, 2014 8:59 AM in response to Doug Lerner2
    Level 1 (65 points)
    Oct 25, 2014 8:59 AM in response to Doug Lerner2

    While I have not seem Mail, when running normally, at ~= 500 MB, a few hundred megabytes is nothing to worry about. The memory issue manifests itself with the rapid, uncontrolled, consumption of many gigabytes of memory.  For *me* it was most definitly a conflict with the Godaddy server and Mac Mail client, and disabling "save drafts on (Godaddy) server" "fixed" the issue.

  • by orionsg8,

    orionsg8 orionsg8 Oct 25, 2014 9:35 AM in response to mswamp
    Level 1 (0 points)
    Oct 25, 2014 9:35 AM in response to mswamp

    I have the same problem, though it happens just with mail open.  I'm running a mac pro with a 500 GM solid state drive, 6-cors Intel Xenon, 3.06 Ghz,  32 GM RAM.  THere's no way I should run out of memory with just word, mail, and calendar open!

     

    This has happened 5 or 6 times since installing Yosemite last week.

     

    Very disappointed with Apple.  A costly and irritating error.

     

    Other issues I continue to experience with Yosemite:

     

    - MS word opens read-only files, obviating changes.  Need to open each file twice.

    - OS fails to recognize shared Mac Air drive, where all my office's files are located.  Connecting to it is troublesome.  And even when connected, applications are unable to save to that location as it fails to show as connected in the save dialogue box (unless the application is defaulting to that folder).

    - cannot post online into text fields without the browser (safari) flashing and fidgeting uncontrollably, can no longer see what's being typed, cannot delete or make changes.  I thought this might be a result of a java update (I had a message that I could not run Illustrator with Yosemite without updating java.  So I reinstalled yosemite, took out the java.  Cannot run Illustrator, but the web post problem still persists).

     

    Can anyone fix these problems?  How do I get rid of Yosemite?  Can I just go back to Mavericks (which was still pretty buggy, but nowhere near as bad)?

     

    Should I just sell this computer, and go back to PC?

     

    *** Apple?

  • by BestOS-OutThere,

    BestOS-OutThere BestOS-OutThere Oct 25, 2014 11:10 AM in response to orionsg8
    Level 1 (0 points)
    Oct 25, 2014 11:10 AM in response to orionsg8

    Dear orionsg8,  please try disabling 'Save drafts on server' for all IMAP  (or maybe just GoDaddy IMAP ) . This temp workaround  at least seems to allow Mail.app to stay running. This tip was shared earlier in this thread. Good luck!

  • by jimkardach,

    jimkardach jimkardach Oct 25, 2014 12:53 PM in response to mswamp
    Level 1 (0 points)
    Oct 25, 2014 12:53 PM in response to mswamp

    Same issue here; I had to stop mail after it gobbled up 51 Gbytes of memory!

    Mail.png

  • by emacinbound,

    emacinbound emacinbound Oct 25, 2014 1:53 PM in response to teonyc
    Level 1 (0 points)
    Oct 25, 2014 1:53 PM in response to teonyc

    Not receiving IMAP GoDaddy Mail has become my main issue now... I have resolved the memory leak with the suggestions in this thread.  Thank you to all who took time to test and provide solutions.

     

    But I an NOT receiving GoDaddy IMAP emails with Mac Mail unless I Take All Accounts Offline and then hit send/receive.   Then and only then do they come through.

     

    Is there another Discussion about this?  This is slowing down my company's productivity and we are missing key emails.   We must now rely upon our iPhone first.   Anyone have anything to share about this?

     

    Thank you.

  • by simplegenius,

    simplegenius simplegenius Oct 25, 2014 2:00 PM in response to emacinbound
    Level 1 (0 points)
    Oct 25, 2014 2:00 PM in response to emacinbound

    Nothing to add emacinbound, except to say that I'm in the same boat, exactly.  My business is suffering in the same way, and I am only aware of the same workaround you are using.  Started back in Mavericks and continues in Yosemite.  Horrible problem and I wish I had an answer for you.

  • by belviking,

    belviking belviking Oct 25, 2014 2:58 PM in response to mswamp
    Level 1 (0 points)
    Oct 25, 2014 2:58 PM in response to mswamp

    cleaning out the drafts folder seems to have fixed the problem for me

    /jm

  • by Thomas Smith3,

    Thomas Smith3 Thomas Smith3 Oct 26, 2014 11:31 AM in response to mswamp
    Level 1 (30 points)
    Oct 26, 2014 11:31 AM in response to mswamp

    There also may be an issue with Safari. I have Safari open with only two tabs open and it is taking over 1/2 a gig of memory see the 2nd, third, and fourth lines in Activity Manager below. When I have multiple Tabs open I can burn 3-4 GIG easily. While not as rapid and catastrophic as Apple Mail it causes a real drain also.Screen Shot 2014-10-26 at 11.15.59 AM.png

  • by jabrewer3,

    jabrewer3 jabrewer3 Oct 26, 2014 5:29 PM in response to Thomas Smith3
    Level 1 (5 points)
    Oct 26, 2014 5:29 PM in response to Thomas Smith3

    Fellow posters,

     

    Please make sure you report these examples of potential issues to Apple. It may in some cases be useful to mention the issue here to provide a fix for other users or to see if there is a common problem set.  But many of us follow the thread and if folks have a new issue you should open a new thread, not hijack this one. 

     

    Also one more request. Once folks have reported success with a fix, the "me too" just adds one more email to our mutual mailboxes..  Like this one does too, but I hope it helps us use the system more effectively.

  • by etresoft,

    etresoft etresoft Oct 27, 2014 5:29 AM in response to jabrewer3
    Level 7 (29,380 points)
    Mac OS X
    Oct 27, 2014 5:29 AM in response to jabrewer3

    jabrewer3 wrote:

     

    Fellow posters,

     

    Please make sure you report these examples of potential issues to Apple. It may in some cases be useful to mention the issue here to provide a fix for other users or to see if there is a common problem set.  But many of us follow the thread and if folks have a new issue you should open a new thread, not hijack this one.

     

    Also one more request. Once folks have reported success with a fix, the "me too" just adds one more email to our mutual mailboxes..  Like this one does too, but I hope it helps us use the system more effectively.

    And to follow up on that, it is important to note that no Apple employees read these forums, officially at least. It is only your bug reports that are officially tracked. Furthermore, do not assume that just because one person reported the bug that Apple is working on it. The Apple bug reporter is a vote-based system. Total number of distinct reports == total number of votes. If there is one bug report and a thread with 1000 replies, that problem does not exist to Apple's eyes. It must have 1000 bug reports too before Apple will consider working on it.

  • by Kirill B.,

    Kirill B. Kirill B. Oct 27, 2014 8:19 AM in response to mswamp
    Level 1 (10 points)
    Oct 27, 2014 8:19 AM in response to mswamp

    +1

     

    Same problem on my 2 of 4 macs with Yosemite!!

     

    Снимок экрана 2014-10-24 в 16.45.03.png

  • by gandalf,

    gandalf gandalf Oct 27, 2014 9:10 AM in response to mswamp
    Level 3 (930 points)
    Oct 27, 2014 9:10 AM in response to mswamp

    Same issue for me with Mail.  The App Store also causes free memory to drop. This really needs fixing.

  • by jabrewer3,

    jabrewer3 jabrewer3 Oct 27, 2014 9:30 AM in response to etresoft
    Level 1 (5 points)
    Oct 27, 2014 9:30 AM in response to etresoft

    Thanks for adding that specific info etresoft.  I hope people read it.  It's more fun to ***** about the problems here, but it is important to be as constructive as possible by reporting them to Apple so they get addressed.  I am going to stop following this thread, since it seems to be complete with the interim solutions.

  • by Thomas Smith3,

    Thomas Smith3 Thomas Smith3 Oct 27, 2014 10:07 AM in response to mswamp
    Level 1 (30 points)
    Oct 27, 2014 10:07 AM in response to mswamp

    OK people the fix is in. Talked with Apple Care Case # 685647934. I firstly did as was suggested by others and unchecked "Store Draft Messages on the Server". Apple Mail:Preferences:Accounts:Select your GoDadday IMAP Account. Then Mailbox Behaviors. Then called Apple Care. They had me reboot using the PRAm Clear. Hit  CMD+OPT+P+R before first ding of reboot. When it restarted  you should see the machine start Ding then Restart and Ding again before booting up. Once you here the second ding you can let up on the keys.

     

    Then we rechecked the "Store Draft Messages on the Server" and no problems since. It seems to have fixed the issue. He left the case open but it has been 24 hours and the latest my Mail client has gone with Memory is 128M, which is normal. So yes report this to Apple Care but this seems to have fixed this.

first Previous Page 9 of 22 last Next