2 Replies Latest reply: Jul 14, 2013 5:20 PM by Linc Davis
khoonseang Level 1 Level 1 (0 points)

process name "securityd" is using high CPU% up to 50% and is causing the fan of the MBA to spin up and draining battery life.

 

I tried to kill it and reboot but that does not help.

 

What could have been wrong?

 

Details:

1. MacBook Air 13" Mid 2012, i5 4GB

2. OS: OSX 10.8.4

 

Thank you

Richard

  • 1. Re: securityd on mac book air
    CT Level 6 Level 6 (15,535 points)

    Does this happen when you login as a different user, e.g., Guest?

     

    Does this happen when starting up in Safe Mode?

  • 2. Re: securityd on mac book air
    Linc Davis Level 10 Level 10 (117,935 points)

    Safari securityd increased processor activity

     

    If the solution in the above thread doesn't solve your problem, continue.

     

    The next time you have the problem, note the exact time: hour, minute, second.

     

    If you have more than one user account, these instructions must be carried out as an administrator.

     

    Launch the Console application in any of the following ways:

     

    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

     

    ☞ In the Finder, select Go Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

     

    ☞ Open LaunchPad. Click Utilities, then Console in the icon grid.

     

    Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select

    View Show Log List

    from the menu bar.

    Scroll back in the log to the time you noted above. Select any messages timestamped from then until the end of the episode, or until they start to repeat. Copy them to the Clipboard (command-C). Paste into a reply to this message (command-V).

     

    When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.

    Please do not indiscriminately dump thousands of lines from the log into this discussion.

     

    Important: Some private information, such as your name, may appear in the log. Anonymize before posting.