Skip navigation
This discussion is archived

Mail - CPU 100%

5369 Views 42 Replies Latest reply: Dec 15, 2008 8:37 PM by Darren 2007 RSS
  • deniskqc Calculating status...
    Currently Being Moderated
    Nov 9, 2008 10:32 PM (in response to CaptPicard)
    Unlike what my friend is saying here, i think hardware failure is still a possibility; and please share any suggestions you may have. My next step is to load the backup from TC to the same MB to see if it would read the Mail normally, just like my MBP does.
    MB black + MBP 2.2
  • Bruce Bathurst Calculating status...
    Currently Being Moderated
    Nov 10, 2008 8:15 PM (in response to CaptPicard)

    You should probably keep 'syslogd' running.

    Your operating system is very busy, juggling a hundred or so little jobs so they appear to all be working in unison (so the 100%, reminiscent of a Microsoft scheduler, is a system bug). Each new startup creates a new system log. (The computer keeps a few.) These are very nice for debugging programs, and the daemon 'syslogd' is always receiving messages from distant parts of your OS and writing them to the latest log file.

    Some applications which produce great quantities of data improperly write these to your console or syslog, but usually it must be kept running. Otherwise, you 'have a puncture without a spare' when things don't go right.

    3B1 SysV, Toshiba T1100 Minix 1.0, Other OS, 10 MHz w/512KB, 20MB HD
  • Bruce Bathurst Level 2 Level 2 (330 points)
    Currently Being Moderated
    Nov 11, 2008 5:15 PM (in response to kocr_mac)
    Just some thoughts.

    Every process runs at 100% for a tiny fraction of a second; but to retain the processor for the length of time sampled by 'Activity Monitor' is a very serious problem. I've noticed that some people here poll their mailer every fine minutes. Recently I received a letter of about 40 MB! (Unthinkable just a while ago.)

    I'm wondering what would happen if your mail didn't complete after 5 minutes, and it polled the mailer again. Pressing the 'Get Mail' button repeatedly is something engineers anticipate. Finding yourself in a situation that would place your mailer in a loop that uses up 100% of the CPU and has to be killed can easily be caused by (bad) programming that is instigated by an unanticipated situation or combination of choices.

    As one used to say in the 70s, 'Take the defaults.' Just something to think about.

    3B1 SysV, Toshiba T1100 Minix 1.0, Other OS, 10 MHz w/512KB, 20MB HD
  • AdiGital Calculating status...
    Currently Being Moderated
    Nov 18, 2008 12:42 AM (in response to kocr_mac)
    I don't use MobileMe, neither have RSS.
    It helped (as for now) when I disabled junk mail filtering. The processor went down to 1%. Re-enabling it left the CPU at 1%. I'm not sure if this completely fixed the problem.
    I have a fresh installation of 10.5 for 2 days and just created one GMail IMAP account in Mail.
    MacBook, Mac OS X (10.5.5)
  • Bruce Bathurst Level 2 Level 2 (330 points)
    Currently Being Moderated
    Nov 18, 2008 1:09 AM (in response to AdiGital)
    Oh, the horrible Junk filter. That would do it. I understand it's easy to create an infinite loop, which is why there is a command at the bottom to stop filtering anymore.

    I've never found good instructions for setting it up; so I normally send all to junk that doesn't satisfy the three checkmarks in the center of the preference. (The boxes that claim to bypass the Junk filter, but are the Junk filter.

    Otherwise, I separate all things that must be satisfied from any one thing that need be satisfied (to be either desirable or spam, as is your preference ) by using separate 'Rules' at the end; but I've never taken the time to study all the documentation on setting up filters. Very important is the order in which the filters are passed through. I haven't a clue.

    So that's a real possibility.


    PS. Oh, disabling the filter is one way of terminating the loop; but it will return when you receive a letter that satisfies those conditions that will again make it circle.

    Edited by bb to make possible to read.

    Edited to try again.

    Edited by bb to add important postscript this time.
    3B1 SysV, Toshiba T1100 Minix 1.0, Other OS, 10 MHz w/512KB, 20MB HD
  • bizmonq Calculating status...
    Currently Being Moderated
    Nov 21, 2008 11:57 AM (in response to kocr_mac)
    Well, I too realized my CPU was working overtime so I checked the Activity Monitor and saw my CPU running at 99.99% with Mail as the culprit. I searched " 100% cpu" and landed on this thread. I read down the list and got to the post where the user identified a recent video attachment as the culprit. That rang a bell as I had just gotten a mail with a .wmv attachment about 12 hours earlier. My MBP had been running smoking hot ever since. So I deleted the mail that I recently received with the .wmv attachment, emptied the trash, shut down and restarted Mail. Problem solved. CPU process when down from 99.9% to 0.2%.
    early 2008 MBP 2.5, Mac OS X (10.5.5)
  • Roland 747 Level 1 Level 1 (0 points)
    Currently Being Moderated
    Nov 27, 2008 8:50 PM (in response to kocr_mac)
    I had the same problem with Mail using 100% CPU.

    For me, uninstalling "Flip4Mac" software (to view WMV files) resolved the problem.

    Note: I double checked by reinstalling Flip4Mac and the CPU immediately went back to 100%.

    Now I just have to find another software to handle WMV files.
    15" Macbook Pro Core Duo, Mac OS X (10.5.5), 15" MacBook Pro Core Duo, 4GB RAM; Windows XP on VM Fusion; Mac OS X (10.5.5)
  • TopoTone Calculating status...
    Currently Being Moderated
    Nov 28, 2008 8:05 AM (in response to Roland 747)
    I've seen some issues pop up with Mail and F4M, related to quicktime. If you have a minute, head over to the F4M support report page HERE, and detail this problem. They are pretty good about updating to fix problems....and might have some info on a workaround, or possible solution. Let us know if you find anything out.
    G5 2 gHz iMac / G4 1.67 15" PB / G4 MDD 1.25/ G3 iBook / 80GB iPod, Mac OS X (10.4.11)
  • Bruce Bathurst Level 2 Level 2 (330 points)
    Currently Being Moderated
    Nov 28, 2008 10:05 AM (in response to TopoTone)
    Just some kludges to offer.

    If your processor is interrupted to process 'Activity Monitor', your scheduler may be working, and the problem may be with an application, such as those listed. This means you can eventually 'force quit' Apple Mail and open it with the ethernet cable unplugged.

    One thing you can try is taking advantage of the IMAP protocol's ability to send you only sender. subject, & existence of attachments, until you request to see the letter. In this way, at least, people plagued with this can read all their mail without attached movies first.

    If you can't find this adjustment, as I can't, you can connect by internal modem (if one still has these), which should automatically put Apple Mail in this mode. Thunderbird (which I use for my spam-catching account), makes adjusting IMAP & POP accounts easy.

    Remember, too, that just a a while ago I lectured a family member on mailing photos totaling 2 MB. Now 40 MB attachments are being mailed! My little DSL is the slowest sold.

    Just some ideas.

    3B1 SysV, Toshiba T1100 Minix 1.0, Other OS, 10 MHz w/512KB, 20MB HD
  • Darren 2007 Level 1 Level 1 (0 points)
    Currently Being Moderated
    Dec 15, 2008 8:37 PM (in response to TopoTone)
    You are absolutely correct as to the cause to the 100% CPU usage with Mail.

    I was finding it would pin previewing an email with a video attached, but it worked great on other messages.

    Unfortunately, I grabbed the latest version and it's still back to 100% CPU usage, but only on an email with a video attached. It's really annoying. The CPU temp jumps to over 70C sitting idle.
     MB, MBP, G4, Nano, ATV, TC, AX , Mac OS X (10.5.5)
1 2 3 Previous Next


More Like This

  • Retrieving data ...

Bookmarked By (0)


  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.