Q: After 10.10.3/sleep discoveryd runs 100% CPU

Just a gentle warning that although your discoverd issues might look like they have been solved after trying one of the many proposed solutions, most have had the issue come back. This is based on reading numerous threads on the net about this problem. the issue may not arise for days or weeks and then suddenly it's back.

I don't think there is a defacto solution. a solution that can claim to actually solve the problem. so beware.

My "solution" is just to unload it and re-load it. I haven't been having any networking issues so far, only issues with CPU usage. when that happens, I unload/reload and move on.

I found the same to be true here (2010 MBA with 10.10.3) but being the moderately iggerant user that I am, I just went to the Activity Monitor and killed the process, knowing it might cause networking problems and being prepared to deal with that. It didn't cause any problems, maybe because discoveryd just reinitialized on its own and was then behaving.

In my case I found that it occurs for me ONLY after a reboot-then-sleep cycle. I reboot infrequently but just did yesterday and today after waking from sleep discoveryd went wild. I killed it and it restarted, and now all is well: I can sleep all I want without it going off the charts, so for me it's just the reboot/sleep that causes it to go erratic and only after the first sleep: killing it and having it restart prevents it from going wild unless I reboot again. YMMV.

Rob, followed most of the useful tips in this thread (except the deletion of the ZZ cache files) to no avail

...but the temp on the left had wrist-rest has being getting hotter and hotter!!!   ...not to mention the underside of my 13" MacBook Pro

called AppleCare today who asked what i'd done etc.

After genuine concerns for my welfare due to it being a possible Apple iNcendiary device

they then had me simply dump the contents of the following:

~/Library/Caches

~/Library/Cookies

~/Library/Saved Application States

{RESTART}

and perform a Secure Empty Trash

right before my eyes the temp began dropping and is currently at a cool 57/59 degrees C on the CPU CORES

I only run Chrome/Safari/Evernote and randomly open iTunes during the day. Very light use most days

...they have kept my case open, while I give it a couple of days testing.

but so far so good

ps: when I sleep and wake, I now DONT see discoveryd

I think we are all experiencing this kind of thing. the problem is that a restart seems to fix the problem but it ends up coming back. it might come back in an hour, a day, a week, a month. but it seems to come back.

i just want to point this out because a lot of people having the discoveryd problem try one of the many proposed "solutions" and some of those people report back that ultimately the problem came back.

So just a suggestion not to do a restart, see a temp drop, and then post that it worked. it will likely not be a permanent solution and it would be a shame for new readers to assume a solution worked because someone pre-maturely posted that it did.

Try the suggestions and wait a week and ensure your mac has been to sleep a number of times before you report success or not.

...but I did do a {RESTART} ?

12 hours on, and with a number of restarts and a shutdown in between, I'm still running cool.

This is the ONLY time my machine has been calm since the 10.10.3 upgrade

(and restarting alone never fixed it for me, it always ramped up once it had slept again)

As I said above, Apple have kept my case open while I give it a couple of days testing and it continues to be good so far...

I may not have noticed the discoveryd  process in the aftermath of the Secure Empty Trash,  as its no longer hogging the %CPU, but it is present.

...it would be a shame to give hope to anyone trying to resolve this issue, eh

your mileage may vary

Plexus wrote:

 

I think we are all experiencing this kind of thing. the problem is that a restart seems to fix the problem but it ends up coming back. it might come back in an hour, a day, a week, a month. but it seems to come back.

 

i just want to point this out because a lot of people having the discoveryd problem try one of the many proposed "solutions" and some of those people report back that ultimately the problem came back.

 

So just a suggestion not to do a restart, see a temp drop, and then post that it worked. it will likely not be a permanent solution and it would be a shame for new readers to assume a solution worked because someone pre-maturely posted that it did.

 

Try the suggestions and wait a week and ensure your mac has been to sleep a number of times before you report success or not.

Thank you so much!! It was really easy and I am now back to normal, the MBP (late 2010) works perfectly. Because of this problem I went to Apple Store Berlin and they told me that I have to change my HD. Have a great week-end!

Vladipiano

Despite the misgivings of Plexus, I implemented this fix on April 19. After I removed preferences.plist, I experienced no recurrence of the problem. Your mileage may vary, but for me the fix works perfectly. Thanks Jerry and Rafael.

Captain Dim

Hey Captain Dim, can you tell use exactly what you did?

So far I have just been unloading and re-loading discoveryd when it acts up. I didn't want to try any of the myriad of proposed solutions because they all felt like shots in the dark. but if you have a defacto solution, I'll try it. just let us know the details (eg. path of files you changed/deleted).

thanks!

goto /Library/Preferences/SystemConfiguration/

Find preferences.plist and trash it.

Reboot.

That’s it.

I agree.

I did this 3 weeks ago and everything is OK.

THANK YOU!!!! That worked perfectly.  Did this 2 weeks ago and it never happened again.  THANK YOU!!!!!!