Xcode 9.3 daemons diagnosticd and homed high CPU usage when running playground

Hi,
Every time I start Xcode and launch a playground (with only on line of code), it is extremely slow to be executed and 2 new daemons are started: homed (takes ~60% CPU usage) and diagnosticd (takes ~150% CPU usage). Killing diagnosticd does nothing, it is immediately restarted. But killing homed will kill diagnosticd too and they never restart after. After having killed homed I'm still able to run my playground.


Steps to Reproduce:

  1. Open Xcode 9.3 (my version is 9E145)
  2. Create or open a playground (with only one line of code, if you want)
  3. If it is configured to run manually, run it
  4. during the phase "Launching simulator", daemons diagnosticd and homed are started -> high CPU usage that never stops


What are these daemon supposed to do ? Is there a workaround to fix this issue without killing the deamon everytime I start XCode and run a playground ?

Thanks,

Xavier Mawet


Edit: I'm not the only one to have this issue, there is a question that has been created recently in stackoverflow for the same issue: https://stackoverflow.com/questions/49591847/xcode-9-3-playground-diagnosticd


Version/Build:

Xcode: 9.3 (9E145)

macOS High Sierra 10.13.4


Configuration:

Mac mini Mid 2011

Processor 2,7 GHz Intel Core i7

8GB RAM DDR3

AMD Radeon HD 6630M 256MB

SSD Sandisk Ultra 2 480GB

Replies

I having the same issue. I do not believe I was having issue with beta's

Macbook Pro (2013)

2.7 I7, 16 GB, NVidia, SSD 1 TB

I’m having the same issue.


  1. Start Xcode
  2. Load a new/old Playground
  3. Simulator takes ~45s-1 min, then opens.
  4. 2 diagnosticd daemons, one mine and the other system’s, run and start cooking my MBP 10.13.4 running Xcode 9.3. 😮


This problem started with the last Xcode beta. I had no problems with previous builds of Xcode running a Playground. 😟


BTW, thanks Xavier for the heads-up on killing the homed daemon as one solution for cooling things.


Update: I filed a bug, 39087027.


Configuration:

MBP 13” (2017)

10.13.4

2.5GHz

16GB

1TB SSD


Build:

Xcode 9.4

Having same issue. Killing homed helps but its annoying to do every time.


Version

Version 9.3 (9E145)


Configuration

iMac (Retina 5K, 27-inch, 2017)

4,2 GHz Intel Core i7

8 GB 2400 MHz DDR4

512 GB SSD

Having this issue too. Funny thing that I was unable to report it using XCode menu Help > Report an issue, as it won't open a bug reporter

I have same issue

Is it resolved by someone?

Having the same issue.

And my playground is set to not run code automatically.

Same issue here.


Version 9.3 (9E145)


Model Name: MacBook Pro

Model Identifier: MacBookPro11,3

Processor Name: Intel Core i7

Processor Speed: 2.5 GHz

Number of Processors: 1

Total Number of Cores: 4

L2 Cache (per Core): 256 KB

L3 Cache: 6 MB

Memory: 16 GB

Boot ROM Version: MBP112.0145.B00

SMC Version (system): 2.19f12

Hi

same problem here with MacBook Pro 17" late 2011,

macOS High Sierra 10.13.4, XCode 9.3.


When I create a new empty iOS Playground

(or use an existing one) with or without executable codes,

a lot of CPU processing power is used by the following processes:

- launchd_sim (227%)

- diagnosticd ( 79%)

until I exit XCode or I kill "launchd_sim" process

Figured I'd join in.


Have the exact same issue going on. Same build of Xcode, same build of High Sierra. Running on a Macbook Pro 10,1. 16GB Ram. 2.6Ghz i7.


Trying to do lessons for online swift tutorial and it's crashing any time. that the playground stays open for more than 3 minutes.

Same Issue - even when creating a brand new default Playground.

Fix: Quit Xcode, relaunch (just don't open any Playgrounds)...


Xcode Version 9.3 (9E145)

macOS High Sierra v 10.13.4

Mac Pro 2013 - Processor 3.7 GHz Quad-Core Intel Xeon E5. Memory 32GB

Yep same here - just filed a bug report.


What I noticed though was homed seems to be generating the following error in the logs and repeatedly retrying:


MediaRemote reply error: <error: 0x110192d20> { count = 1, transaction: 0, voucher = 0x0, contents =

"XPCErrorDescription" => <string: 0x110192fc8> { length = 18, contents = "Connection invalid" }

}


[DistantDiscoverySession] ERROR: Failed to fetch hosted routing XPC endpoint. Will retry. Error Domain=kMRMediaRemoteFrameworkErrorDomain Code=1 "Unknown Error" UserInfo={NSLocalizedDescription=Unknown Error}


I will attempt to find out more about this error and if I find anything relevant will post back here


My configuration is:

Xcode Version 9.3 (9E145)

macOS High Sierra v 10.13.4

iMac (Retina 5K, 27-inch, Late 2015)

Same issue, CPU temp goes over 70C.


macos High Sierra 10.13.4 (17E199)

MacBook Pro (Retina, Mid 2012)

2.3 GHz Intel Core i7

8 GB 1600 MHz DDR3


Apple, what the ****???


(is there an auto-sensor to remove cursin' ??)

I've created a bug report six days ago but still have no answer. The case hasn't been treated yet! How it's possible to make an xcode release with such big bugs

Same issue here!


Two days ago I was running macOS Sierra and Xcode 9.2 without any problems. Updated to High Sierra because it is required to run Xcode 9.3

Starting or opening any playground results in two diagnosticd processes with very high CPU usage. Also takes a long time to run the playground!

The homed process is also rniing @ 52% CPU!


Mac Mini 2011 16Gb Ram

High Sierra 10.13.4

Xcode 9.3

Similar issues here. It's make it very difficult to work in playgrounds. I don't have a solution, but it seems that others are chiming in with system information.


Version/Build:

Xcode: 9.3 (9E145)

macOS High Sierra 10.13.3


Configuration:

MacBook Pro (Retina, 13-inch, Early 2015)

Processor 2,7 GHz Intel Core i5

16 GB 1867 MHz DDR3

Intel Iris Graphics 6100 1536 MB

APPLE SSD SM0256G