Bad luck with MacBook 5,1 and Yosemite. Sloppy.

Discussion in 'OS X Yosemite (10.10)' started by east85, Aug 21, 2015.

  1. east85 macrumors 65816


    Jun 24, 2010
    Yeah, it's an older MacBook so I can kind of see why the operating systems seem less and less optimized for this hardware. When Yosemite first came out I did a clean install as I did in the past with Lion, Mountain Lion, and Mavericks, none of which has caused me any issues. Yosemite however progressively got worse update after update. After updating I almost always perform an SMC reset and clear the PRAM.

    At first Safari started exhibiting a bad memory leak, eating upwards of 5GB of RAM and constantly beachballing me, frustrating as Safari is all I really like using. Looks like Apple removed the "Reset Safari" option a while back. 10.10.3 crashed the entire system while updating and caused me to restore from a backup. Sloppy. After I updated to 10.10.5 my system started crashing regularly and shutting down. Really?

    I think that's when I had enough, wiped everything. Installed 10.10.5 fresh and haven't had any issues so far, but as you could expect I am quite weary about updating. Never before has an Apple OS given me so much trouble. And I know it's not the fault of my hardware, diagnostics show everything is fine, also the MacBook is operating fine under a clean install.

    It's just frustrating, crossing my fingers in regards to future updates.

    Anyone else have a similar experience on older hardware?
  2. Taz Mangus macrumors 68040

    Taz Mangus

    Mar 10, 2011
    It is hard to say why you were having the issue you had. I have updated a 2009 Mac-Mini, 2009 MacBook Pro and a 2011 27" iMac and have not seen anything like you experienced. I always try to use the combo updater if possible. Not sure if it makes any difference, I just feel better using that for an update.
  3. east85 thread starter macrumors 65816


    Jun 24, 2010
    Yeah typically I will do the combo updater as well.

    Oh well, Safari seems to be OK so far. It's been using 300MB-400MB, a far cry from the 4GB of ram it was sucking up before.

Share This Page