Slashdot Mirror


Mac Users Reporting Widespread System Freezes With OS X El Capitan 10.11.4 Update (macrumors.com)

An anonymous reader quotes a report from Mac Rumors: A large number of MacBook Pro owners running OS X El Capitan are reporting widespread system freezes since installing the 10.11.4 update to Apple's Mac OS. The problem appears to be concentrated on 13-inch Retina MacBook Pros (Early 2015) running 10.11.4. Users report that their system becomes totally unresponsive at seemingly random times, with no way to regain access to their Mac other than to force a hard reboot. The issue was initially reported by MacRumors forum member Antonnn on March 25, four days after Apple released what is the third update to the Mac OS. In Antonnn's case, the freezes have been occurring "about once a week," first when browsing in Safari, but then also during the use of other Mac apps, including Adobe Photoshop and several third-party browsers. The freeze seems to affect not only the screen and mouse cursor but also the Mac's Force Touch trackpad, which completely loses feedback. Apple Support is apparently aware of the issue but have so far offered no concrete solution. Meanwhile, some users have resorted to downgrading their system to 10.11.3 by restoring from a Time Machine backup or performing a clean install. Hundreds of others have posted to a dedicated thread discussing the issue. Bill Mattheis posted a video on YouTube of the freezing he has experienced on his MacBook Pro.

14 of 100 comments (clear)

  1. There I was by subk · · Score: 2

    All ready to make first post.... but my Mac Book Pro froze!

    --
    Now, if you'll excuse me, I have backups to corrupt.
  2. It could happen to anyone... by ndykman · · Score: 5, Insightful

    But, the advantage Apple has always had is a very small set of hardware configurations, but if you let a bug like this out the door, you aren't taking nearly as much advantage of that as you should. So, actually, I do hold Apple to a higher standard here, because they need to be. You don't get to set exactly what computers run your OS, and how much they will be and then turn around and say, "oh, that obvious bug we let out the door, it happens, what can you do"

    Take the ASUS motherboard UEFI boot problem. Microsoft had admit the problem, post a workaround, and didn't even mention the thousands and thousands of other hardware combinations that worked just fine, because nobody cares anyway. But, if I was an OSX users, I would be upset. The damn things should just work and trudge along, update after update for a few years. But they increasing don't do that, and people paid the premiums for the platform anyway and thank Apple for it. Just stop thanking them for a start.

  3. Lies by 110010001000 · · Score: 4, Funny

    Ridiculous. I updated three days ago and I havent s

  4. Never moving to El Capitan by Sir+Holo · · Score: 3, Interesting

    I will never move to El Capitan.

    It kills too much software – including the $2700 Adobe Creative Suite Master Collection (basically everything Adobe). I have way too much expensive deisgn, scientific, and creative software to waste two days determining which ones will break. And at any rate, Adobe's asshole move to push people to CC (renting software you use to make a living) alone is a deal-breaker.

    BTW, I have several pieces of software that I purchased a very long time ago – back in the days of Carbon – that still work just fine. That is, they ran OS X 10.1, and still do on OS X 10.10 with no updates of the programs. Examples are Audion, Mineteur, and many others.

    1. Re: Never moving to El Capitan by Anonymous Coward · · Score: 2, Interesting

      You're running PowerPC software on OS X 10.10 even though Rosetta doesn't work on 10.7+?

    2. Re:Never moving to El Capitan by gtall · · Score: 4, Funny

      "It kills too much software – including the $2700 Adobe Creative Suite Master Collection (basically everything Adobe)."

      Count your blessings.

    3. Re:Never moving to El Capitan by dgatwood · · Score: 2

      Personally, I blame Adobe for deciding to stop selling software and forcing everybody to rent it. I'm still using Photoshop CS6, and gradually transitioning new content creation away from Adobe products in expectation that eventually I'll have to treat it as a legacy application and run it in a virtual machine when a future OS update breaks it.

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    4. Re:Never moving to El Capitan by Sir+Holo · · Score: 2

      Huh? I am running that suite on EL Capitan and have no problems. Go back to your bridge troll...

      I have read it in many forums. I do not have the time to take the risk of wasting a day installing El Capitan, and then potentially cloning my backup to recover.

      In web-searches, I've found that people are overwhelmingly having problems with the Adobe Creative Suite in El Capitan, versus those who have no problems. I don't have the spare time.

      If you have any tips, I would love to hear them. Which applications in the Suite do you use? Which have you not tried with El Capitan?

      And, to reply to another Commenter –– I have been programming and building computers since 1985. MacBook Pros are not designed to be user-serviceable, but I have upgraded and extended my Macs (and PCs) since the 1980's. Yes, first was a PCjr in the 1980's, and then an Apple IIe later on.

      I have three "dead" MacBook Pros on my couch. Each will take me about an hour to repair, and to bring up to current standards. Hell, I brought a 10-year-old MacBook (white, 1st rev after clam-shell) back to life, such that the friend felt like she had a 'new computer'.

      I typically get called an Apple Fan-boi. Now I get called an anti-Apple Troll. Which is it, dear Peanut Gallery?

    5. Re:Never moving to El Capitan by flyingfsck · · Score: 2

      Uhh, a bit more than 5 minutes - since you have to re-install the OS after swapping the SSD. I bought a Macbook for a niece and the damn thing failed after 2 weeks - been fine since - so I know exactly how much work it was to replace, re-install and reconfigure.

      --
      Excuse me, but please get off my Pennisetum Clandestinum, eh!
    6. Re:Never moving to El Capitan by macs4all · · Score: 2

      So, what you are saying is that you never upgrade RAM or hard disk drives? You never replace the hard disk to get a larger drive or faster SSD over the course of ownership?

      Your comment is silly, and you should feel silly typing it.

      You need to learn to READ. I said:

      If you have a laptop, AIO, or cylindrical computer like nearly all Mac (not "Hack") owners,and you have to take it apart more often than once every half-decade, then it is your computer (and/or you) that has a problem.

      Well, if we're talking about a recent laptop, most of them have soldered-in RAM; so nevermind that upgrade.

      My 2013 MacBook Pro still has RAM sockets; but that is about the last year you'll find them on nearly any laptop, from any manufacturer. In fact, there is some sort of Windows standard that REQUIRES soldered-in RAM (can't remember the stupid MS name for it). And since Apple computers are Certified for Windows, I would imagine that applies to them, too.

      As for HDD/SSD, sure. But if you are upgrading those more often than every half-decade, something is wrong in your personal ability to spec hardware properly; or you are just one of those insane people that absolutely MUST have something new every 6 months. Again, see "can't spec hardware properly."

      That's why I put the qualifier on it of "every half decade". You chose to ignore the qualifier and turn it into an absolute "never"; which I CLEARLY didn't say.

      So, it is actually YOUR comment that is silly, and you should learn to read.

  5. Re:Problems of scale by bloodhawk · · Score: 2

    If hundreds or thousands are reporting it then it is like affecting several orders of magnitude more systems, by the sounds of things you need to be running the system continuously for a while too so I would say this is likely something easily discovered for them. Most users will simply hard boot and move on. I will never forget a technical gig I had about 20 years, I had to go into help out a design company, the users were furious as their new Windows NT machines would blue screen once a day and it was unacceptable they needed stability like their Mac's. While I was their fixing a driver problem I witnessed there Mac's mac's crash approximately every 45 mins to 1 hour, When I commented on it. they said "no they do that every hour, but we don't have to touch them they just come right back up after a few minutes", apparently the Apple engineer had convinced them this was normal behaviour. So I set Windows NT to auto reboot on blue screen of death instead of sitting there with its thumb up its arse. It is amazing what some users will put up with if they think it is normal.

  6. El Capitan has other problems by DrTime · · Score: 3, Informative

    My install of OS 10.11 in October 2015 seemed to be terrific. Then I found that had trouble with SDHC cards on my 2009 iMac 27". It might read and write cards after a clean cold boot, but it also might self reject them, and it never would even see a SDHC inserted after a sleep cycle. Others reported similar issues, one post on the topic was up to 9 pages a few weeks ago on the Apple Discussion forum. The problem was reported on many different models, not all were old.
    10.11.1, 10.11.2, and 10.11.3 brought no relief. Then, 10.11.4 improved its operation substantially. SDHC cards would work for several sleep cycles before being gone to the wind. Sometimes, just to be assertive, OS X 10.11.4 reverts to its old ways. It likes to mess with me.
    I have never had El Capitan freeze on me BTW.
    10.11 El Capitan brought a whole new USB software support and some people have claimed various fixes for the SDHC issue, use a driver for an external reader, muck with the control files for USB, etc. The reliability and security of these fixes is always dubious.
    Other problems also came with El Capitan (for me at least). Calendar spins its color wheel cursor at me as type in new events, it takes 5 or more seconds to respond to a single character. I've played with the various iCloud settings and mitigated the problem, but not by much.
    El Capitan came with a number of "improvements". The Notebook application was supposed to have numbering and other new features. I tried them and couldn't believe how poorly the features worked. I looked for an alternative and discovered the best application on the planet, Microsoft OneNote. I now use it on my Mac, my iPhone, my Chromebook, my Windows bootcamp partition, and at work on the PCs. Highly recommended. Best app I've ever used.
    The myth of "it just works" is a myth. I curse my Macs oddities way more than I curse at the PCs at work, except for cursing at the work itself.
    I toyed with restoring Yosemite from my Time Capsule. I finally did a few weeks ago, but to an external Firewire disk. Then I found that using an external disk for booting OS X doesn't work that well. It won't wake from sleep well, for example. But I tried, I just don't want to blow away the internal disk for it. Any besides, it took 6 hours to build that disk from Time Capsule as it restored 650MB of media besides the OS plus all the old versions of my software. You have no (minimal) control over Time Capsule.
    There is nothing Apple sells that I want any part of anymore. The new iMacs look just like the one I've been using. Maybe my problems with El Capitan are due to my computers age, but I buy Apple because they've historically given me good value and lasted with full software updates. Like for seven years now.
    I may have to switch to Windows one day. Don't tell me about Linux, I use it all day at work too. Not Ready for Prime Time.
    So, I guess I'd rather bitch than switch.

  7. Re:macbook air by Sperbels · · Score: 2

    Coincidently, my Air just froze 10 minutes ago while viewing an animated gif in Safari.

  8. Can confirm this... by mlts · · Score: 2

    I do have a 13" MBP, and about every two weeks, it will be unresponsive when I SSH or RDP into it, and a screen lock pops the pinwheel of death...forcing a hard shutdown.

    Even more quirky, if FileVault is in use, upon reboot, it will block the keyboard input for a random duration (30-60 seconds), allow keyboard/mouse movement for 100-500 milliseconds, then block it again. To get around this, if I don't do a "fdeutil authrestart" as a way of rebooting, I have to clear the NVRAM, and after doing that, it boots without issue... until it is time to restart again. Initally, with 10.10, I didn't have that issue until the update last August. 10.11 seemed to clear that up until about 2-3 months ago when it came back.

    I know Apple can do better than this. They control the vertical and horizontal with their hardware. My 2008 MB (first unibody aluminum model) is still going strong, after a battery, SSD, and RAM update. The 15" MBP I use has zero issues with it. My iToys work flawlessly.

    Even though Macs are not Apple's cash cow, it would be nice if Apple could either pay more attention to them, or if that isn't the company's focus, spin Macs off into a separate company that can focus on making the absolute best x86 hardware out there.