Where to report this issue related to Playground?

I need a short confirmation where I should report issues related to Swift Xcode Playground.

I cannot test the behaviour in < Xcode 9.3, but in the latest version there are two diagnosticd instances spawned on my system (10.13.4).

One of those is related to Xcode:

  • /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot/usr/libexec/diagnosticd.

There is also a homed spawned:

  • /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/CoreSimulator/Profiles/Runtimes/iOS.simruntime/Contents/Resources/RuntimeRoot/System/Library/PrivateFrameworks/HomeKitDaemon.framework/Support/homed

The issue is that the diagnosticd instance related to Xcode spikes up to ~150% CPU usage and the other one uses ~80% CPU, while homed is around ~60% CPU usage. Playground is completely idle and does not contain any code that should be compiled or run. Those processes keep running constantly with such high CPU usage and heating up my CPU dramatically by +40°C from ~30°C up to 70°C or higher. :exploding_head:

This does not happen in a normal Xcode project, only Playground is affected.

When in doubt, I'd file a Radar. For what it's worth, while I did see this behavior in Xcode 9.3, I can't reproduce it in Xcode Version 9.4 beta (9Q1004a). I'm sure it wouldn't hurt to have a duplicate, though.

1 Like

If you do file a radar, please indicate it is probably a duplicate of 39102147 (I filed that one) and 39085132 (which I found here: Xcode 9.3 Playground - diagnosticd - Stack Overflow). I haven't tried 9.4 beta, but I will now as the bug makes playgrounds unusable due to extreme slowdowns.

1 Like