Is Google Chrome Causing Your MacBook Air To Crash? Could Be.

By

MacBook Air

Gizmodo reported today that their new MacBook Air was crashing something fierce. They turned to their own forums and the Apple Support forums and found that many other users of the MacBook Air also had the crashing issue. Both parties saw improvements when they stopped using Google’s star web browser, Chrome, but no one could be sure.

They even checked on the MacRumors forums, finding the same issue. Then, they heard from Google.

Later in the day, Google contacted Gizmodo, telling them the following:

We have identified a leak of graphics resources in the Chrome browser related to the drawing of plugins on Mac OS X. Work is proceeding to find and fix the root cause of the leak.

The resource leak is causing a kernel panic on Mac hardware containing the Intel HD 4000 graphics chip (e.g. the new Macbook Airs). Radar bug number 11762608 has been filed with Apple regarding the kernel panics, since it should not be possible for an application to trigger such behavior.

While the root cause of the leak is being fixed, we are temporarily disabling some of Chrome’s GPU acceleration features on the affected hardware via an auto-updated release that went out this afternoon (Thursday June 28). We anticipate further fixes in the coming days which will re-enable many or all of these features on this hardware.

So, while it’s good to know what’s going on, users of Apple’s latest MacBook Air hardware who are experiencing crashes (I’m not, but my Air is from last year) might check for an auto-update of Google Chrome, or stick to Firefox and Safari until Google fixes the main issue.

Source: Gizmodo Via: 9to5Mac

  • Eric_M_White

    I have actually had similar problems with my 15″ MacBook Pro. I have had kernel panics that trace back to the graphics cards. I uninstalled Chrome and the computer has gotten better.

  • Kenton Presbrey

    I had a lot of Kernal Panics on my MacBook Pro after I upgraded to Lion from Snow Leopard. I tried reverting back to SL and reinstalling Lion again..Same thing. So I installed a fresh copy of Lion and Poof! Back to acting like an OSX machine. I haven’t had a single system crash since. I also, haven’t had a single system crash on any of my machines I bought with Lion preinstalled. I feel like their is some sort of an issue with upgrading and that was what was causing all of the problems people were having with Lion. Needless to say I will be installing a fresh copy of Mountain Lion in July. I cannot wait for that upgrade.

    (early) 2011 15in MacBook Pro 2.2GHz i7 8GB 240GB Vertex 3 SSD /// (mid) 2011 27in iMac 3.4Ghz i7 16GB 256GB AppleSSD + 1TB /// (Late)2011 13in MacBook Air 4GB 256GB SSD

  • pixelbud

    I wrote about this yesterday. Not just Air, has been my 13″ MacBook Pro too. http://garybacon.com/post/chrome-causing-new-2012-macbooks-to-crash/

  • Gergith

    To be fair, both Apple and Google have glitches in their products. Googles glitch, which SHOULDN’T crash the computer triggers Apple’s glitch which DOES crash the computer… So the headline SHOULD read “Is the way Apple handles Chrome causing all these crashes?”. or something to that effect. Google’s “fix” is to disable a number of features that it SHOULD be able to use and DOES on other hardware, but causes crashes on these specific Apple products. Good thing Chrome runs well on both my 2011 MBA and Mini server :)

  • Gergith

    Do you understand what a kernel panic is and why it happens? In this case it is the system reacting to a security risk of the system, so to prevent further risk to the system or data corruption, a kernel panic is tripped, allowing a safe reboot of the system. My question is, what the fuck are google up to and is this an attempt to circumvent the sandboxing security features? Don’t be so fucken blinded by google. They’re as evil as the best of them.

    Yes… You do realize that even if Google is maliciously attempting to exploit a security hole… that Apple is the one responsible for that hole right? If Apple can’t create a sandbox that actually works and prevents software writers from being able to trigger Kernel Panics, then the OS itself is written wrong…

    This used to be a HUGE problem on windows, but Microsoft appears to have figured out how to deal with it. The rate of bluescreens of death (or black) has been reduced drastically. Something Apple could do as well…

  • Felfac

    trolling google….