Fans and memory bog down

Discussion in 'MacBook Pro' started by TheKaveman, Jan 27, 2013.

  1. TheKaveman macrumors newbie

    Joined:
    Jan 27, 2013
    #1
    Macbook pro late 2010 2.53 GHZ core i5 with 8gbs memory installed


    After doing fairly basic memory intensive tasks computer fans turn on at full speed and memory becomes bogged down

    http://www.flickr.com/photos/92368436@N05/8395334105/in/photostream

    After ending most processes, computer fans continue to run at full rpm and do not turn off. Memory seems to lag as well

    http://www.flickr.com/photos/92368436@N05/8395334191/in/photostream

    I proceed to shut lid of computer and fans then turn off as computer goes to sleep. when I wake the computer memory bogging is elminated and fans turn off and no lag.

    http://www.flickr.com/photos/92368436@N05/8395334277/in/photostream

    The following photos show all processes in Activity monitor.
    The computer is working fine in this photo for roughly one minute before fans kick on

    http://www.flickr.com/photos/92368436@N05/8395432011/in/photostream

    Computer then repeats as before and bogs down. all processes are shown.

    http://www.flickr.com/photos/92368436@N05/8395432241/in/photostream



    I have tried resetting SMC, and have used many different programs to clear caches and memory. Computer does not even feel hot to the touch when the fans turn on and after all programs are ended. I have also regulary cleaned computer so no debris is obstructing fans. I have taken the computer to an apple store and they ran testing on memory and graphics cards. They also reinstalled newest OS and updates. At first, I thought this resolved the issue but backing up using time machine caused the same situation. Any Ideas?
     
  2. snaky69 macrumors 603

    Joined:
    Mar 14, 2008
    #2
    The Activity monitor is clearly showing your machine is getting quite taxed, 3 adobe apps nearly maxing out your processor in that last screenshot. What you're experiencing is perfectly normal for a computer being pushed like that.

    I don't see what your problem is? But if it bothers you, nothing short of a more powerful(read newer) machine will help you. You're not running out of memory, you're running out of processing power.
     
  3. TheKaveman thread starter macrumors newbie

    Joined:
    Jan 27, 2013
    #3
    I agree the adobe programs are quite taxing. However, after I proceeded to shut down all applications and set the machine at idle, the Kernel Task is still running way to high on CPU usage and this doesn't go away until I close the computer lid or restart it

    This photo shows all processes ended

    http://www.flickr.com/photos/92368436@N05/8395488481/in/photostream
     
  4. snaky69 macrumors 603

    Joined:
    Mar 14, 2008
    #4
    It could be a lot of things, kernel_task is very generic. I'm thinking maybe your computer is Indexing the folders where you worked? This has a tendency to give the machine quite a workout...
     
  5. TheKaveman thread starter macrumors newbie

    Joined:
    Jan 27, 2013
    #5
    That could be a possibility, because right now the fans are at max rpm and the computer is extremely laggy with only safari open and i'm currently backing up my computer with time machine. Any recommendations? I clear caches often.
     
  6. derbothaus macrumors 601

    derbothaus

    Joined:
    Jul 17, 2010
    #6
    Turn off time machine. It slows things down as well.
    Try updating photodownloader's camera RAW. It seems to be working way too hard and too often if you are not actively downloading photos. Maybe not use it to test:)
     
  7. TheKaveman thread starter macrumors newbie

    Joined:
    Jan 27, 2013
    #7
    Running only safari and time machine and nearly 200% CPU usage allotted for kernel task still doesn't sound right to me. The machine isn't that outdated.
     
  8. derbothaus macrumors 601

    derbothaus

    Joined:
    Jul 17, 2010
    #8
    No it is not right. Have you sorted why Adobe downloader is using so much anything and if that could possibly be leveraging kernel after the fact? You really need to look through your console logs.
     

Share This Page