• On CBS MoneyWatch: 20 Worst-Paying College Degrees
advertisement
August 27, 2009 10:40 AM PDT

Apple's Mail maxing CPU usage

by CNET staff

Edited by Joe Aimonetti

Some users have experienced an issue where Apple's Mail application will use 100% of the CPU and eventually fail, causing the system to slow down and overheat.

According to users in this Apple Support Discussions thread Mail will unexpectedly max out the CPU and eventually cause the entire system to overheat. Poster "Ranger Ric" reports:

"I recently noticed that my Macbook Pro was bogging down and overheating. Also, Mail would unexpectedly quit after about 30 minutes every day. Upon diagnosis I fond that the Mail app was running the CPU at 100+% all the time. I tried a fresh pref file and it did not help. The CPU should only run a few percentage points on Mail."
The issue appears to be related to SyncServices and how it relates to managing Mail. With the help of a neighbor, "Ranger Ric" was able to devise this solution:
"Make sure Mail, Address Book and Safari are closed (write down these steps). In Terminal type:
/System/Library/Frameworks/SyncServices.framework/Resources/resetsync.pl reset
Start Mail again.

By the way, doing this will cause Sync to need to ask you whether you want to merge or overwrite data on either MobileMe or your computer. I assume everyone reading this post is familiar with the fact that if you choose merge you may duplicate every record in your calendar, address book, bookmarks, etc. If you know your local files are OK (and have made backups) I suggest you choose to overwrite MobileMe, but that is up to you.

This fix seems to work so far as Mail has been running cool now for a few hours. Post back with your experience."

When attempting this solution, it is important that you create a stable backup of all your important data. If you are worried about possibly deleting contacts, export a vCard of your entire Address Book before attempting this workaround. Several users have reported that this fix seems to have solved the issue.

Experiencing problems? Have feedback? Let us know!
You can now follow MacFixIt on Twitter!

Resources

  • this Apple Support Discuss...
  • Let us know!
  • Twitter!
  • More from Late-Breakers
  • Recent posts from MacFixIt
    iTunes 10 user interface sees some minor changes
    Apple seeds iOS 4.1 Gold Master to developers
    Possible fix for Harman Kardon iSub problems with PowerPC Macs
    Precautions to take before installing iTunes 10
    A reminder on how to reset your Mac's system password
    Mail messages appearing blank
    Adobe Lightroom update brings direct Facebook publishing; Camera Raw 6.2 released
    Weekly troubleshooting utilities update
    Add a Comment (Log in or register)
    by b-dog August 27, 2009 11:31 PM PDT
    In December 2008 I had this problem for several months on my 2.4GHz Macbook Pro. Tried all the usual troubleshooting - disk repair, permissions, prefs delete, etc, as well as a few arcane terminal commands (that I no longer remember - it was last year). All to no avail.

    If I left Mail running on my computer at night, in the morning I'd find that it had been running all night with one CPU pinned at 100%. This happened a few times and I think it may have caused some kind of heat damage, because the computer was starting to experience frequent kernel panics, and soon after that one of the ram slots ceased to work with any ram installed. I could only run with one stick of ram in one specific slot, otherwise the computer would crash during start up.

    I called Applecare and explained the situation. Despited the fact that my laptop's warranty had expired a few months previously, they extended my warranty so I could have it checked it out.

    Unfortunately, the repair required a logic board replacement, but fortunately, Apple paid for it. For that at least, I'm grateful. The laptop is now my girlfriend's and it's working fine.
    Reply to this comment
    by kucharsk August 28, 2009 10:45 AM PDT
    Running the text command advised above is no different than simply following the advice Apple gives here:

    http://support.apple.com/kb/TS1627
    Reply to this comment