kernel_task is using 100% CPU when waking from sleep

That's what I posted earlier in the tread. Been using safari for the last week and no issues. If I leave chrome open and close the lid wait a minute or 2 and open it I get high kernel_task. Close chrome and close the laptop and wait another minute or 2 and then open the laptop kernel_task drops off. So for me it is chrome.

I've seen it happen on a stock MacBook so I'm not sure it's chrome.. Mine has been acting up lately while using the microphone, so perhaps google chrome accesses the microphone for some reason? My computer used to do it with audio output, and now it seems to only do it on input. I have the most issues after using voice chat in Steam. Hope this helps!

Chrome does use the mic. I have the hot word plugin installed. I will try uninstalling it.

Unfortunately, I use Firefox and rarely run Chrome and I've been suffering through this. I don't believe it's any one app as you can see from my history, Apple tech blamed it on my Drobo driver to which Drobo claimed it's definitely not. Plus, I'm having a difficult time replicating this bug. Sometimes it happens and other times it doesn't even if I'm performing the exact same task. And sometimes restarting doesn't always fix it whereas other times I could have my computer running for 24 hours and waking from multiple sleeps and the problem isn't replicable. Incredibly frustrating.

I don't have Hot Word installed.

So it seems the problem is related to the sound driver and it happens when Chrome is running.

If someone from the Apple staff is reading this: I'm available for testing and giving more details to help correcting this problem.

I can replicate the problem on my Mac:

1. Open Chrome
2. Go to sleep
3. Wait 5 minutes
4. Wake it up

I've had it happen on a fresh 10.9.1 install with no 3rd party apps.

However, I do use Chrome, and I do use hot word. When I disabled hot word, kernel CPU went back to normal.

Then I closed Chrome, waited a minute, and close the laptop (mid-2013 AIR), reopening another minute later and CPU was pegged again...

I've found that if my battery is less than 100%, and I connect the power adapter while close, wait for the magsafe to turn orange and open, it's 50/50 that the CPU will be normal. If I open not connected to the power, it's pegged 100% of the time.

Is there a way to disable the sound driver/hardware (like an rmmod)?

OK, some corrections:

I can replicate the problem on my Mac (mid-2013 air, power adapter plugged in):

1. Open Chrome
2. Go to sleep
3. Wait 5 minutes
4. Wake it up

I uninstalled hot word and then tried to recreate it and so far it has not happend. But I will give it a few days and see. It may not be Chome it might be the way an app access the mic or sound driver. So to the person who said they have it and are on Firefox I would look at a plugin or app that is accessing the sound. For me it seems it was the hotword plug in chrome.

Sorry everyone, but there is so much junk being discussed here its really wasting everyone's time. Of course Apple have propogated most of the red herrings, such as Drobo stuff above.

I never use Chrome. I have never even heard of Hot Word. I can get this problem with NO APPS RUNNING. Restarting doesn't fix it more than 1 in 3 or 4 tries. I have rebooted 4 times today, and still my machine is running like a dog. Apple don't care, it's as simple as that. Likewise, I don't care much for Apple any more, having been one of their biggest fans in the past.

Mavericks has huge memory leaks, and many bugs they are not addressing for some reason. Maybe they have a contract with the NSA, maybe that's why this "problem" can't be "fixed". 😉 😀

Yea my kernel/audio issue occurs with audio in general (Safari, iTunes, w/e) - I haven't tried Chrome.

Blaming the NSA won't solve anything...

still 10.9.1 didn't solve the problem...

very disapointing

Just tested without Chrome and still get the 100% CPU.

Chrome seems not to be at fault...

....i have this on several MacBook´s (Air), also on MacBooks of friends. Different configuration. One work around work everyware:

a) start iTunes (or another Audio app)

b) close MBA

c) wait 10 sec

d) open: 100% Task go down

BUT: Apple, please fix it!!!!!!!!!!!

Herby, you are talking rubbish I am afraid. "One work around work everyware"......... Yeah? What about on a **** iMac, where you can't close it?! It is way deeper than any of these random ideas, which may work on one machine, but they are not THE cure, or THE workaround at all. The only workaround I have found so far in my case, is to shut my computer down and walk the dogs in the field. When I do that, the kernel task doesn't occur as the machine is off. Not sure if the dogs have anything to do with it.