Skip navigation
This discussion is archived

Quick Look Helper hogging up 189% of CPU

3197 Views 6 Replies Latest reply: Dec 17, 2010 1:59 PM by Network 23 RSS
cam2099 Level 1 Level 1 (5 points)
Currently Being Moderated
Dec 11, 2010 5:29 PM
For the first time ever, I heard my MBP fan when I wasn't even using it to begin with. No apps opened, etc. It drained my battery pretty good too from 75% down to 33% in a matter of 25 minutes I'd say. Anyways, since I didn't have anything opened I launched Activity Monitor and the only thing hogging up CPU/Memory was the Quick Look Helper process.

I went to restart and it wouldn't restart. I then went to Force Quit to see if there was something "hanging" up the system, but only saw the Finder listed in there. I just went ahead and relaunched Finder and restarted the system again. This time it restarted.

Any idea what would cause this and how to prevent it from happening again?
MacBook Pro - iPhone 4 - Airport Extreme, Mac OS X (10.6.5)
  • bobbyco57 Level 4 Level 4 (1,745 points)
    Currently Being Moderated
    Dec 11, 2010 6:17 PM (in response to cam2099)
    Similar situation for me a few weeks ago...
    From Applecare Support Rep.
    Relaunch Finder. If not resolved then
    Restart your Mac and reset the PRAM.
    How, you ask...
    As soon as you hear the chime sound press and hold the following 4 keya
    Command, Option, P, R
    Keep holding them until a couple seconds after you hear the chime repeat itself.
    Your machine will reboot refreshed.

    As to what's happened. If it happens once, it's a fluke basically. If it happens frequently resetting PRAM is supposed to resolve the problem though I didn't get a specific explanation.

    I know there is a tech note somewhere on Apple Support site with the official procedure for resetting PRAM, you can search for it if interested.
    15" MB Pro 6,2: 2.8Ghz, 500GB, 4GB, Mac OS X (10.6.5), iLife 11, FCE 4.01, iDevices, ATV2
  • S.U. Level 6 Level 6 (8,360 points)
    Currently Being Moderated
    Dec 11, 2010 7:12 PM (in response to bobbyco57)
    MBP 17" hi res, 2.4 GHz Core 2 Duo, 4GB RAM, 500 GB HDD, Mac OS X (10.6.5), iBook G4, 800 MHz; PowerMac G4 867 DP(MDD); PB G3 PDQ; PB 145B; 12" PB G4
  • cgapperi Calculating status...
    Currently Being Moderated
    Dec 17, 2010 12:39 PM (in response to cam2099)
    Just caught my machine doing the same. Possible solution found here: for some. However, I am not running VMWare and do not find the culprit qlgenerator mentioned in this thread. My qlgenerators are:

    MacBook Pro 15", Mac OS X (10.6.5), 2.53 Intel Core 2 Duo, 6GB RAM
  • Network 23 Level 6 Level 6 (11,500 points)
    Currently Being Moderated
    Dec 17, 2010 1:59 PM (in response to cam2099)
    I've only seen that when I had some large photos and I suspected QuickLook was choking on them. I believe I came up with that conclusion after looking at the system log in Console and noticing filenames. Do you see any error messages in the system log that refer to QuickLook and specific files?
    Mac Pro, MacBook Pro, iPhone 3GS, Mac OS X (10.6.5), PowerBook G4 15" Al, PowerBook G3 FireWire, PowerCenter Pro, PowerBook 160


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.