Mountain Lion: Mail uses 100% cpu

Hi Vrenna

Thanks for the response.

My Exchange account is not setup in Mail, that broke when upgrading from Snow Leopard to Lion. I've been using the webmail interface (for the exchange account) ever since.

So I have two imap and two pop accounts setup which was fine in Lion, even though the proxy blocked the imap accounts.

Now Mail hogs the CPU and RAM when I leave it running when using the proxy.

Regards

Paul

Some additional info...

This morning, I took the two imap accounts offline, but Mail was sill hogging the CPU. So I quit it.

Then later, I had to check something so I restarted Mail. While waiting for it to start I got busy with other work.

Much later I noticed that Mail CPU usage was 0%, so I thought Mail fixed itself... Only later on did I realise that one of the Pop accounts did not sign in.

One of my accounts I must accept the connection because of a certificate issue. As soon I connected to that Pop account the CPU usage shot up again :-/

So it might not be a imap issue after all...

I am having this issue too. It's really slowing down my machine. I've been googling "sluggish Mountain Lion" since I installed a few months ago. I can confirm it is happening on both my Macbook pro and mac mini.

After looking at activity monitor, discovered mail is always at LEAST above 100%, sometimes goes to 200%+.

I have multiple accounts including pop, imap, and exchange.

If I read this correctly it seems a bug has already been filed...

https://discussions.apple.com/thread/3950156?start=15&tstart=0

I don't want to talk too soon but it seems that 10.8.2 has fixed this issue of Mail going into a panic when behind a proxy.

Been on the network for 30 minutes and Mail using almost no CPU and RAM. If it stays like this I will try and setup my exchange account again next week sometime.

Can any of the others confirm that 10.8.2 fixed this issue?

Thanks Apple!

I tried this today behind the firewall at my office and I can also report that Mail is not using more than normal amounts of CPU even with my IMAP accounts online. I think it's safe to say that Apple worked this one out.

Thanks, guys!

Here is the problem. I solved it permanently by diactivating a problematic email account. It just worked.🙂

The latest fix didn't solved the problem in my iMac.

10/17/12 4:16:24.008 PM Mail[4093]: Keychain sandbox consume extension error: s=-1 p= Cannot allocate memory

There's the message that dominates the console for me. Mail takes 165% of my CPU. I am at a hotel. Could it be related to the WiFi server here?

The console looks like this and goes on and on wiht the sandbox message. I get the pinwheel and locked out.

10/17/12 4:16:21.257 PM Mail[4093]: Using V2 Layout

10/17/12 4:16:21.766 PM Mail[4093]: Loaded NSBundle </Users/TimmyR/Library/Mail/Bundles/MailTags.mailbundle> (loaded)

10/17/12 4:16:21.790 PM Mail[4093]: Initialized MailTags Bundle 3.1.4b2043 NSBundle </Users/TimmyR/Library/Mail/Bundles/MailTags.mailbundle> (loaded)

10/17/12 4:16:21.921 PM Mail[4093]: MailTags: Loaded Script Suite Registry

10/17/12 4:16:21.925 PM Mail[4093]: reading TagsFor all Messages

10/17/12 4:16:21.927 PM Mail[4093]: MailTags database Current version: 8, required Version 8

10/17/12 4:16:21.927 PM Mail[4093]: Tag Cleanup: searching for messages no longer in Mail

10/17/12 4:16:21.995 PM Mail[4093]: Tag Cleanup complete

10/17/12 4:16:22.028 PM Mail[4093]: Finished Reading Tags For 12180 Messages

10/17/12 4:16:22.067 PM MailTagsSparkleHelper[4101]: Sparkle App Launched! Target Bundle: MailTags.mailbundle notification: NSConcreteNotification 0x7fc72141c490 {name = NSApplicationDidFinishLaunchingNotification; object = <NSApplication: 0x7fc720422950>; userInfo = {

NSApplicationLaunchIsDefaultLaunchKey = 1;

}}

10/17/12 4:16:22.071 PM MailTagsSparkleHelper[4101]: Performing background Sparkle Check for MailTags.mailbundle feedURL http://www.indev.ca/sparkle/MailTags3.xml

10/17/12 4:16:22.075 PM ubd[4096]: Warning: accessing obsolete X509Anchors.

10/17/12 4:16:22.211 PM com.apple.SecurityServer[15]: Session 100021 created

10/17/12 4:16:22.396 PM librariand[4095]: MMe quota status changed: under quota

10/17/12 4:16:22.509 PM ubd[4096]: Warning: accessing obsolete X509Anchors.

10/17/12 4:16:22.625 PM ubd[4096]: Warning: accessing obsolete X509Anchors.

10/17/12 4:16:22.657 PM MailTagsSparkleHelper[4101]: updater did not find update

10/17/12 4:16:22.657 PM MailTagsSparkleHelper[4101]: updateDriverDidFinish: NSConcreteNotification 0x7fc72107d0d0 {name = SUUpdateDriverFinished; object = SUScheduledUpdateDriver </Users/TimmyR/Library/Mail/Bundles/MailTags.mailbundle, /Users/TimmyR/Library/Mail/Bundles/MailTags.mailbundle>}

10/17/12 4:16:22.743 PM ubd[4096]: Warning: accessing obsolete X509Anchors.

10/17/12 4:16:22.862 PM ubd[4096]: Warning: accessing obsolete X509Anchors.

10/17/12 4:16:22.896 PM Mail[4093]: Keychain sandbox consume extension error: s=-1 p= Cannot allocate memory

10/17/12 4:16:22.896 PM Mail[4093]: Keychain sandbox consume extension error: s=-1 p= Cannot allocate memory

10/17/12 4:16:22.896 PM Mail[4093]: Keychain sandbox consume extension error: s=-1 p= Cannot allocate memory

10/17/12 4:16:22.897 PM Mail[4093]: Keychain sandbox consume extension error: s=-1 p= Cannot allocate memory

10/17/12 4:16:22.897 PM Mail[4093]: Keychain sandbox consume extension error: s=-1 p= Cannot allocate memory

10/17/12 4:16:22.897 PM Mail[4093]: Keychain sandbox consume extension error: s=-1 p= Cannot allocate memory

10/17/12 4:16:22.897 PM Mail[4093]: Keychain sandbox consume extension error: s=-1 p= Cannot allocate memory

10/17/12 4:16:22.897 PM Mail[4093]: Keychain sandbox consume extension error: s=-1 p= Cannot allocate memory

10/17/12 4:16:22.897 PM Mail[4093]: Keychain sandbox consume extension error: s=-1 p= Cannot allocate memory

10/17/12 4:16:22.897 PM Mail[4093]: Keychain sandbox consume extension error: s=-1 p= Cannot allocate memory

10/17/12 4:16:22.897 PM Mail[4093]: Keychain sandbox consume extension error: s=-1 p= Cannot allocate memory

10/17/12 4:16:22.897 PM Mail[4093]: Keychain sandbox consume extension error: s=-1 p= Cannot allocate memory

10/17/12 4:16:22.897 PM Mail[4093]: Keychain sandbox consume extension error: s=-1 p= Cannot allocate memory

10/17/12 4:16:22.897 PM Mail[4093]: Keychain sandbox consume extension error: s=-1 p= Cannot allocate memory

10/17/12 4:16:22.898 PM Mail[4093]: Keychain sandbox consume extension error: s=-1 p= Cannot allocate memory

10/17/12 4:16:22.898 PM Mail[4093]: Keychain sandbox consume extension error: s=-1 p= Cannot allocate memory

10/17/12 4:16:22.898 PM Mail[4093]: Keychain sandbox consume extension error: s=-1 p= Cannot allocate memory

10/17/12 4:16:22.898 PM Mail[4093]: Keychain sandbox consume extension error: s=-1 p= Cannot allocate memory

10/17/12 4:16:22.898 PM Mail[4093]: Keychain sandbox consume extension error: s=-1 p= Cannot allocate memory

10/17/12 4:16:22.898 PM Mail[4093]: Keychain sandbox consume extension error: s=-1 p= Cannot allocate memory

10/17/12 4:16:22.898 PM Mail[4093]: Keychain sandbox consume extension error: s=-1 p= Cannot allocate memory

10/17/12 4:16:22.898 PM Mail[4093]: Keychain sandbox consume extension error: s=-1 p= Cannot allocate memory

10/17/12 4:16:22.898 PM Mail[4093]: Keychain sandbox consume extension error: s=-1 p= Cannot allocate memory

10/17/12 4:16:22.898 PM Mail[4093]: Keychain sandbox consume extension error: s=-1 p= Cannot allocate memory

10/17/12 4:16:22.899 PM Mail[4093]: Keychain sandbox consume extension error: s=-1 p= Cannot allocate memory

10/17/12 4:16:22.899 PM Mail[4093]: Keychain sandbox consume extension error: s=-1 p= Cannot allocate memory

10/17/12 4:16:22.899 PM Mail[4093]: Keychain sandbox consume extension error: s=-1 p= Cannot allocate memory

10/17/12 4:16:22.899 PM Mail[4093]: Keychain sandbox consume extension error: s=-1 p= Cannot allocate memory

Bump...

Does anyone have any further suggestions? I am going make the drive to the Apple Store on Sunday if I cannot resolve. My MacBook will NOT run Mail. I've delted plist file, and Mail from Library; I have removed all mail accounts and tried to start over. Nothing works.

The two dominant messages in Console are

10/19/12 9:37:59.049 AM Mail[1366]: Keychain sandbox consume extension error: s=-1 p= Cannot allocate memory

10/19/12 9:38:06.803 AM syncdefaultsd[1373]: Warning: accessing obsolete X509Anchors.

Console will kick out over 4000 messages as a result of trying to start Mail and access Preferences.

I have the same issue too! Mail is constantly at 100% and because of that, the fan on my Mac will go on like a plane about to take off even when I'm doing light tasks like word processing or internet surfing. I hope someone can help...

Just tossing this in, in case Apple Support is adding up reports. I just ran into this issue too, after noticing a Mail slowdown and thinking it should not be happening on this i7. And I'm on battery power at the moment, which means I don't need sandboxd chewing up the CPU and my battery life.

Mail currently eating 300% CPU and has been for the last 15 minutes or so. Restarted after happened previously. Mail now unusable, can't fetch or read messages.

If someone can point me to where I can find a useful log, happy to post it.

Have you found out the solution to this? Right now, Mail is running at close to 300% CPU. Pretty hilarious, I think, and also scary to force quit the client.

I had this recently on a client's new iMac. First I deleted the email that had a 254MB attachment, from the mail server....😮 (I kid you not).

You can delete stuff directly off the mail server by selecting the account in the left hand column of Mail, then Control click and select Account Info. You will then see a list of emails still on your host's mail server. Anything dodgy, delete it (careful you don't delete anything you haven't downloaded yet). This is also a good way to check how full your mailbox is if you have a cap.

Also, go to the user library (in Finder hold down Option and click on the Go menu, select Library) open the Caches folder and trash the contents. Don't worry these are all temp files and will be recreated where necessary, but they can get corrupted.

This cured my particular problem, YMMV.