Benches macOS

15

High CPU usage in Mail

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

I was notified of and installed a system update yesterday. I don't know if this issue happened immediately thereafter, but I've been seeing it today. CPU usage hits about 100% for Mail. I usually have to force quit.

I have several IMAP accounts configured, all on different servers, and I've tried disabling and/or taking each of them offline to see if there was something specific to a server, folder, etc. No dice.

When using the Activity window in Mail, it seems fairly consistent that the CPU spike coincides with Mail's attempt to synchronize the Apple Mail To Do folder. Has anyone seen this? Is it a bug in the latest update, or just coincidence? Any suggestions?

15 replies

Sign in or join Beachball Help to reply.

  1. 0

    Mulder

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Does Mail crash? If so, post the crash log so we can see what it says (we only need the header and the portion for the actual thread that crash; the rest won't help).

    If it's a To Do failure, you may get a crash. If you want to try the fix for that to see if it solves your problem, do this:

    1. Quit Mail

    2. Open iCal and delete all your To Do items, then quit iCal.

    3. Start Mail and see if the problem is still there; if not, try adding back your To Do items to iCal one at a time and testing between each one to see that Mail still launches normally with no hogging of the CPU.

    Mulder

  2. 0

    colemj

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I also have the problem of Mail pegging the CPU usage and causing high heat. This started happening immediately after upgrading to 10.5.4 using the combo updater. It is reproducible and happens after sending an email.

    Mail behaves and uses almost no CPU while in the background or while reading mail or composing mail. As soon as I send an email, the CPU immediately ramps and the computer gets very hot. Mail then won't quit and has to be force quit.

    When relaunched, everything is fine until I send another email. I have repaired permissions and verified the disk using Disk Utility. It also happens on all three accounts I send email from.

    Any help would be greatly appreciated

    Early 2008 MBP 2.4GHz 4MB 10.5.4

  3. 0

    Mulder

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Are you using HTTPMail and/or GrowlMail? If so, it's probably HTTPMail that is causing the problem; remove it and then restart Mail.

    Mulder

  4. 0

    colemj

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    No, I don't have either of those - just the Mail app as it came from Apple. I created a new user account and don't experience this problem from the new account. So something is causing it in my local account. I will look for conflicting add-ons.

  5. 0

    DeathscytheSephiroth

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I also have this issue too and sometime i can't quit Mail the quit command in menu bar is gray and i can't click it

  6. 0

    ns

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I have both symptoms:

    - Mail periodically (after a couple of minutes of being open) hogs nearly 100% of CPU resources. Best that I can tell, it is neither fetching nor sending email at that time.

    - Mail refuses to Quit. It has to be Force Quit every time.

    In addition, Mail also crashes when clicking on Notes and ToDos.

    I have 2 IMAP (including MobileMe) and one POP account. There is not much traffic in my Mailboxes. These issues appeared about the time of 10.5.4. Mail not quitting seems to be somewhat pervasive if posts here are an indicator.

    I have tried everything that people here have suggested, short of re-installing the OS. Mail is near useless for me as of now. I am patiently waiting for a patch from Apple.

    (The Genius Bar fellow did not have any solutions either.)

  7. 0

    kokooi

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I also have similar problem. Whenever, mail run, there is almost 100% CPU usage. When I use freepopsd, it is definitely going to be 100% cpu usage. I can't erase junk mail. I have reinstalled OS 10.5 then use 10.5.4 combo updater to update the os. Subsequently, I download each and every update to update manually - not using the software update. In between updates and installation, repairing of permission and clearing caches were done.

    Problem remains.

    Furthermore, the powerbook also shutdown by itself.

  8. 0

    Telecart

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Same issue. Once in a while I realize my computer has really slowed down, I open up activity monitor to see that mail.app is eaiting away 90 of my CPU. Haveto force quit it to go away.

  9. 0

    Encecu

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I've the same problem since a couple of days ago. I haven't any ToDo's in iCal, so I can't delete anything.

    By the same time I started to use MobileMe and synchronizing some Mail issues. Have any of you experienced conflicts between Mail and MobileMe features?

  10. 0

    ns

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Encecu,

    I believe most of the people who are having certain problems with Mail (high CPU usage, crash on quit or need to Force Quit, etc.) are using MobileMe. I am using that service and am really REALLY frustrated with Mail and its antics. I have tried many potential troubleshooting steps that have been offered here.

    One user reported that if he disabled the MobileMe mail account, all his problems (Force Quit and high CPU usage) went away. Disabling MobileMe is not a practical solution for me, so I am waiting for Apple to offer some help in terms of an update.

  11. 0

    Encecu

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Thanks, ns. I've made a backup of mail folders and preferences in /Users/XXX/Preferences and I've deleted all original files. When I set up my IMAP account again all worked fine (I haven't lost any mail), even my new MobileMe account appeared totally configured.

    The problem seems to continue with my gmail account, with currently can't be synchronized in Mail.

  12. 0

    Telecart

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I'm not a MobileMe user, same issue.

  13. 0

    RichardStarr

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Are you all trying to access IMAP accounts? I'm having the same experience on my MacBook Pro, which is at 10.5.4. Accessing the same email accounts on my G5, which is still using Tiger, is no problem. One thing I notice in the activity panel (command-0) is frequent, unexplained hangups in caching. I think the latest version of Mail.app on Leopard has some serious bug when trying to communicate with IMAP servers.

  14. 0

    saint-georges

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Thank you for starting this thread. I had been so annoyed with Mail using 100% (since much longer than 10.5) than I kept on using the old Eudora that I used since 1995. Because the iPhone is very link with mail I start again Mail, tried anything to stop this Global warming producer :

    - I switch from POP account to IMAP

    - I follow advice from the thread : stop Me account, destroyed all the To Do (doesn't matter because I start to use OnniFocus that interface with iCall and iPhone) and all the notes (considering Ever Note that interface with iPhone).

    But nothing changed… Like a clock Mail.app is using nearly 99% of the CPU.

    Mail.app is like many non pro app not a good app.

  15. 0

    Madiba

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I have the same 100% CPU usage issue. I have one IMAP account, and don't use MobileMe. In Activity Monitor Mail is the culprit with around 99% CPU usage. I cannot send in a crash report because Mail hasn't actually crashed (yet) because of this.