5 Replies Latest reply: Jul 12, 2010 2:25 PM by alphadork
Thepyro395 Level 1 Level 1 (0 points)
I have had my macbook for awhile and it was working just fine. As of recent it started to run very hot even when it isn't running any major app at all. Why would that be?

Macbook 13(unibody), Mac OS X (10.5.5)
  • Jay Bullock Level 4 Level 4 (3,800 points)
    When it begins running hot, do you also notice slowdowns/ spinning beachballs? Are you using something like iStat to make sure your fans are actually running?

    iStat widget:

    When you notice the MacBook running hot, go to Applications/ Utilities/ Activity Monitor. Change the pull-down in the middle to "All Processes" ("My Processes" is the default) and then sort by the CPU column. Is there a process that is spiking your CPU?
  • James Mosher Level 1 Level 1 (10 points)
    Try to reset the PRAM. Restart the computer while holding down Command, Control, P, & R keys. My processor was running at 170 F + and after PRAM rest runs between 130 and 150. Hope this helps.
  • jaguar724 Level 1 Level 1 (0 points)
    something called LOCUM is running over 100.0.
    i don't know what that is but it's running from root. please advise
  • Jay Bullock Level 4 Level 4 (3,800 points)
    Locum is a process that runs when you're emptying the trash, particularly large deletions or secure deletions. Have you been emptying the trash a lot lately?

    If the process runs for a long time, and the trash is not in the process of being emptied, you can use Activity Monitor to kill the process.
  • alphadork Level 1 Level 1 (5 points)
    I was having a similar problem - CPU temp would shoot up over 190 degrees, fans would noisily rev up to 6000+ rpm, and both iStat and the Activity Monitor showed "Locum" using over 100% of CPU (I assume that means 100% of one of two cores - not that it matters).

    I had checked the Finder preference (Finder > Preferences > Advanced) for secure deletion, and although I wasn't aware of the correlation, I believe these events were happening when I was emptying the trash.

    Unchecking that setting would appear to have fixed the problem.