Mountain Lion freezing constantly

Discussion in 'OS X Mountain Lion (10.8)' started by kirkbross, Sep 30, 2013.

  1. kirkbross macrumors 6502a

    kirkbross

    Joined:
    Mar 6, 2007
    Location:
    Los Angeles
    #1
    I know there are a billion threads on this already, but I thought I'd start a new one.

    • 2008 Mac Pro w/ ATI 5770 viddy running 10.8.5.
    • Freezes constantly forcing hard power downs. Suck.
    • Pressing power button gives me a Shut Down/Restart/Log Off dialog, but... I am helpless to interact for the non-responsive keyboard and mouse.
    • Seems to happen mostly when Chrome is open.
    • Apple hates Google, Google hates Apple.
    • I have hardware acceleration disabled.

    Thoughts besides "don't use Chrome?"
     
  2. Weaselboy, Oct 1, 2013
    Last edited: Oct 2, 2013

    Weaselboy Moderator

    Weaselboy

    Staff Member

    Joined:
    Jan 23, 2005
    Location:
    California
    #2
    Does it only ever happen when using Chrome? I use Chrome and never see this.

    Maybe try a command-r boot to recovery and start Disk Utility then run verify disk to see if there are any disk errors. Also try running the Apple Hardware Test.
     
  3. MeUnix macrumors 6502

    Joined:
    Aug 21, 2013
    Location:
    San Francisco
    #3
    I also use Chrome regularly and haven't experienced any type of freeze. Seems like it could be something else forcing your Mac to freeze. I'd run a hardware test, like another member suggested.

    - Kyle
     
  4. Spacial macrumors 6502

    Joined:
    Aug 29, 2013
    #4
    Mountain Lion & Chrome work great for me. Couldn't be better.
     
  5. TheBSDGuy macrumors 6502

    Joined:
    Jan 24, 2012
    #5
    That could be the hard drive. ***Could*** being the keyword there. If there are bad sectors on the drive and Chrome is stored on or using one (or more) of them, then any time you run Chrome you'll run into the problem. You may also see it occur erratically with other programs because head crashes/bad blocks/bad sectors often span many contiguous areas.

    I use Scannerz to test my drive, but don't go out and throw money at a tool until you try a couple of things first.

    First, go to the Applications folder and rename Chrome to something else (like _Chrome.app or NaughtyChrome.app …whatever you want…using whatever words you want). Then download and install Chrome again, run it, and see if the problem persists. With luck ML won't be aware of the older install of Chrome and do a fresh install.

    By renaming the original Chrome, your basically keeping all the blocks associated with that application intact but not in use. Installing the new Chrome should install on good blocks. If the drive encounters bad sectors during that installation, it should theoretically re-map them to spare sectors unless you're out of them.

    Assuming you install the new Chrome and everything starts working great, then the drive likely has some bad sectors on it. In that case you might want to check out Scannerz and some of its documentation at:

    http://scsc-online.com


    There's a fair amount of info in both their downloads section and how-to section. A tell tale sign would also be that running the older, renamed version of Chrome still causes problems.

    If the problems persist you might have a system problem, like with RAM or something. Possibly Chrome is accessing some regions of RAM or Video RAM other apps don't reach and there's a problem with them. Another possibility is that you have some type of library incompatibility problem, which is difficult to isolate (on the web anyway). You could check the RAM and other system problems by using Apple Hardware Test which might be revealing.

    Last but not least, ML is very, very picky about versions and hardware. I'd make sure all your software and Chrome itself are up to date.

    ...of course you could always just not run Chrome....:D
     
  6. kirkbross thread starter macrumors 6502a

    kirkbross

    Joined:
    Mar 6, 2007
    Location:
    Los Angeles
    #6
    I've narrowed this down to happening almost exclusively when I Quit Chrome, either with a CMND+Q or Menu > Quit.

    I've turned off all the acceleration in settings and it didn't help. I can't seem to find a solution so I just avoid Chrome.

    It seems to happen more when I've been surfing a while and / or have several tabs open, vs. if I just open Chrome and immediately quit.
     

Share This Page