cpu pegged-safari-interesting result

Discussion in 'MacBook Air' started by rroback, Mar 20, 2008.

  1. rroback macrumors member

    Joined:
    Jun 29, 2007
    #1
    So I've read about all these people having core shut downs, and all sorts of temp issues, and I haven't had any, with my 1.8/ssd. I've used youtube, played some hd stuff.. nada. Last night, I went on a youtube frenzy, played a bunch of videos, and it got warm, but the fans kept the machine cold, and after I stopped, cpu temp and usage dropped, and the machine went silent.

    this morning, I watch some videos, and the temps go way up ( 80), and they've hit that high before, but only briefly. They stayed at between 70-80, and I even closed the videos, and one cpu remained pegged. I had one window open in safari, and it was pegged. So, I closed safari, and the usage instantly dropped, and the temp dropped 9 degrees. Now, I'm a little confused. I understand safari must have proccesses that remained in action, but that temp drop, is well, close to impossible. Anyone have any idea how accurate the temp sensors, and more importantly, istat is? either way, if your system is pegged, it might be worth closing, and reopening safari. I'm cruising at 48 degrees right now, pretty normal.
     
  2. antibact1 macrumors 6502

    Joined:
    Jun 1, 2006
    #2
    I have a SR MBP and I have had this problem with Safari a couple times in the last week or so, but never before. Things will seem normal but my fans all of a sudden rev up. Closing Safari fixes the problem - annoying though. Would be concerned to leave my computer on and unattended like I used to with my PowerBook.
     
  3. SirReel macrumors newbie

    Joined:
    Aug 21, 2007
    #3
    I too see an issue now and then where Safari gets hung up like that. In fact, that is the only time I ever see core shutdowns. Anyway, I notice that if I get into that condition, I can even close all the Safari windows and the background process is what seems to be hung up, only a full Quit of Safari. I then, like you, see immediate CPU and Temp drops via iStat. The only conclusion I've been able to come up with is that the default refresh rate for the Temp in iStat is set to 10 seconds, at least mine was. So, I'm assuming the temp drop actually happened during that time frame, so when the number changes, it looks like an instant drop. I've changed the setting in my iStat, but, haven't had the condition occur yet. Hopefully the next time it happens, the Temp will show a steady quick decline instead of the insane jumps like we have seen currently. Otherwise, I'm :confused:
     

Share This Page