New 2012 Macbooks, Google Chrome, and Kernel Panics

Call Apple Care and see what they have to say about the matter. Since it's their product, they would know whether there is a known issue or not. Or take your computer to an Apple Store within your 14 days and have the staff there check it out.

Hi,

13inch i7 new MBP here. I got the same crash with Google Chrome. Laptop made a loud sound before rebooting. I hope they admit it's an issue and find a fix for it 😟 I sent my crash report.

It seems to be a problem with many new MBPs (non-Retina) as it's been a frequent topic of discussion both here and on other forums. Whether it's a Google Chome problem or a MBP problem, it's pointing toward a MBP problem. I'd just use Firefox or Safari until a 'fix' is found - on either end.

Clinton

Hey,

Same issue here. 13inch mid 2012 MBP. It froze several times, a guy called me from Apple and asked me to send him some logs. I believe it's a software problem, maybe a new driver for Intel HD 4000 (?) or software update will solve this. During this last 3 days my MBP never froze, except once while I was playing Diablo 3 (the days before it froze many times while using just Chrome and even once while running Blizzard Launcher for Diablo 3)/

Having the exact same issue. I originally purchased an 11 inch 2012 Macbook Air and returned it for the 13 inch model and both of them crashed multiple times when using Google Chrome. Seems like it is effecting all of the models with the HD 4000.

The 13 inch Air I have now straight up freezes and becomes unresponsive and I have to power it down. Here's the message that's in all of my error logs:

BSD process name corresponding to current thread: Google Chrome He

I had a quick chat with Apple support on the phone and was told to try Safari. Problem is Chrome is far better for development work and I use it every day.

Please come out with an update!!!!

Please come out with an update!!!!

jw,

I'm not sure who is the 'guilty party' here - Apple or Google. If I were you guys, I'd fill out a bug report with both Apple and Google. Apple can be found here and here's a forum for bug reports for Google Chrome (does Chrome come with it's own bug reporter, a la beta versions of Firefox?).

Anyway - get the ball rolling!

Clinton

Thanks, I went ahead and reported a bug to both Apple and Google. 🙂

This is an Apple software bug in the com.apple.driver.AppleIntelHD4000Graphics kernel extension.

Each of these panics is occurring at the instruction at offset 0x8a01 into the extension.

This is not the fault of Chrome or Final Cut Pro or of any other application, it's a bug in the kernel extension.

You can either wait for an Apple software fix or return your MBP for a refund - it's your call.

But there's no reason to debate it any further.

The software is broken, Apple needs to fix it and you can wait for a fix or not, period.

A different MBP will eventually trip over the same panic if it's simply a kernel software bug.

Some folks are running Google Chrome Canary - https://tools.google.com/dlpage/chromesxs?platform=win - and not having any problems.

You could give it a try, at least...

Clinton

My brand new Macbook Air 2012 is going the same thing when I'm running Chrome. It happened to me 3 times yesterday, so as others have suggested I tried running the Canary build. That resulted in the 4th kernel panic.

Seems Canary isn't immune either.

Each crash report had this line listed:

"BSD process name corresponding to current thread: Google Chrome He"

I have MacBook Pro 13', 2.9 GHz, 8Gb. Bought on June 2012.

I have the same issue with the line after the restart:

"BSD process name corresponding to current thread: Google Chrome He"

Sometimes it freezes and I have to force shut down and sometimes it restarts by itself.

I have tried to install Chrome beta and also Canary instead of regular Chrome but all 3 of them give me the same problem.

See this link - http://www.appleinsider.com/articles/12/06/29/google_admits_chrome_bug_responsib le_for_crashing_macbook_airs.html - a lot of people have been blaming the kernel panics on Apple: now it seems that Google is taking the blame.

But you get to pick whose side your on!

Clinton

GOOLGE CONFIRMED THAT THE ISSUE IS BECAUSE OF CHROME. PLEASE CHECK THE PRESS NOTE BY THEM BELOW

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.

Source: http://gizmodo.com/5921609/new-macbook-air-crashing-blame-google-chrome-probably

No - William Kucharski says that it's an Apple problem and he has a lot more points than I do!

Clinton

Have 15" pro retina Since June 21 (29 today)

Using Firefox - no issues.

However ... when opening the lid, and on wakeup, I've had 3 kernel panics and restarts.

I generally close all apps before closing the lid.