Previous 1 2 3 4 Next 58 Replies Latest reply: May 19, 2014 7:49 PM by dje0986 Go to original post
  • MBPr Level 1 (0 points)

    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.

  • Hangover. Level 1 (20 points)

    Well. could be. I can't comment on that as I am not that keen into code things

  • markbrads Level 1 (0 points)

    You seem to know what you are talking about, could you look at my Kernel Panic below and see if you think my issue is also HD4000 Apple related as I have never used chrome but I have about six Kernel Panics in five days.


    Thanks in anticipation.


          Kernel Extensions in backtrace:

   [6B02D782-A79F-399C-81FD-353EBF F2AB81]@0xffffff7f816c5000->0xffffff7f8172bfff

                dependency:[C0404427-3360-36B4-B483-3C9F0C54A3CA]@0xffffff 7f80847000

                dependency:[474FE7E9-5C79-3AA4-830F-262DF4B6B544]@0xff ffff7f80cbd000

                dependency:[EF26EBCF-7CF9-3FC7-B9AD-6C0C27B89B2B]@0 xffffff7f80c84000



    BSD process name corresponding to current thread: prl_vm_app



    Mac OS version:




    Kernel version:

    Darwin Kernel Version 11.4.2: Wed May 30 20:13:51 PDT 2012; root:xnu-1699.31.2~1/RELEASE_X86_64

    Kernel UUID: 25EC645A-8793-3201-8D0A-23EA280EC755

    System model name: MacBookPro9,2 (Mac-6F01561E16C75D06)



    System uptime in nanoseconds: 10143415415864

    last loaded kext at 6018355847640:          4.1.19 (addr 0xffffff7f807c9000, size 16384)

    last unloaded kext at 6079420291626:          4.1.19 (addr 0xffffff7f807c9000, size 12288)

    loaded kexts:

    com.parallels.filesystems.prlufs          2010.12.28

  • jag2009 Level 1 (0 points)

    Nope, see that line that says:

    BSD process name corresponding to current thread: prl_vm_app


    That means the process that caused your crash was your Parallels Virtual Machine.

  • jag2009 Level 1 (0 points)

    FYI - for everyone keeping track, Google has officially acknowledged this issue and is in part due to the current Chrome build, and in part due to an issue with the Apple drivers even allowing an application to trigger a kernel panic (meaning the OS shouldn't even be allowing an application to crash the whole machine at all).


    More info from CNET on the whole issue here (including the statement from Google): macbooks/


    In the short-term, you can run the Google Chrome dev channel which has installed a temporary workaround while they dig into the underlying issue. You can download a .dmg package to install the Chrome Dev channel here:


    The version that includes the workaround is: Version 21.0.1180.15 dev.


    To see what version you are runing, go to "Tools > About Google Chrome", and if it's any number less than the version above, then you don't have a ver with the temp fix.


    Also, you can keep up to date with the issue by following Chrome's release blog here:

  • William Kucharski Level 6 (14,985 points)

    As I mentioned before, Google Chrome is causing the resource exhaustion, but Apple needs to fix the fact that the kernel panics when it occurs and handle the resource exhaustion intelligently.

  • pranayt Level 1 (0 points)

    Its in warrenty better take it to apple genius store.. They will sort your problem or replace it.

    It might be a logic board problem.

  • Yufeii Level 1 (0 points)

    @pranayt are you saying it's a hardware problem??


    Don't return your mac or bring it to the apple store. It's not like they can do anything and they can take your mac to get it fix, or you get a new one with the same problem, since it's a software issue.


    Just wait patiently for a chrome and apple fix. I think since chrome already pushed the auto-update it shouldn't be happening anymore.

  • Patopipp Level 1 (10 points)

    Or maybe Apple releases a firmware update that fixes this problem, or Mountain Lion will be the solution.

  • markbrads Level 1 (0 points)

    Hey Patopipp,


    I know what you mean but It's unfair users should wait for a new OS to get a product working, why didnt Apple wait to release the MacBooks till Mountain Lion.


    I cant help thinking this didnt happen in the past (if you know what I mean)

  • rolandp43 Level 1 (0 points)

    I alos experienced this, the screen stops responding, what i have to do is to re-start by pressing the on-off button to turn it off and then re-start, but I read some good advise, open a youtube video, then right click and then turn off the hardware accelaration...

  • eyeknownuffin Level 1 (0 points)

    I've read everyone's post particular the gear listed and all I can contribute is that my 2-day old 2.3Ghz Retina Display MacBook also crashed twice and it has Mountain Lion. So for those of you expecting a solution via an OS upgrade, well it looks like we'll have to wait a little longer.

  • jag2009 Level 1 (0 points)

    FYI - since moving to the Chrome dev channel, my machine has not crashed since. Chrome even did crash once, but it didn't take down the whole machine.


    You can follow my directions above to install the Chrome dev channel in place of the affected versions of Chrome.

  • Ducman Level 1 (105 points)

    Is mountain lion available now in Australia?

  • eyeknownuffin Level 1 (0 points)

    Sure is. advertised as from July 1 though I picked up the Retina Display June 30 & that's what it already had loaded.