diagnosticd for simulated apps "kills" the system
| Originator: | futuretap | ||
| Number: | rdar://32533185 | Date Originated: | June 2 2017, 1:43 PM |
| Status: | Duplicate/25618147/Open | Resolved: | |
| Product: | Developer Tools | Product Version: | 10.12.5 |
| Classification: | Performance | Reproducible: | Always |
Summary: When simulating an iOS app in the Simulator, I sometimes notice "diagnosticd" taking up 200% CPU and more. Currently I see two diagnosticd processes spinning at 130% and 70% respectively. They take roughly 5 minutes to complete their work and go back to 0% CPU again. Steps to Reproduce: I can reproduce the issue when my simulated app is backgrounded in the iOS Simulator. Expected Results: I question if it's actually useful to run diagnosticd on simulated iOS apps. There are better tools for developers to do performance analysis than a diagnostics report that is buried somewhere deep on the disk. Also, I think it's not very useful when diagnosticd spins up for minutes at 200% just because there was a (much less severe) performance problem of the app being diagnosed. Observed Results: see above Version: Xcode 8.3.2 (8E2002) macOS 10.12.5 (16F73) Notes: I'm attaching you a sample and spindump of diagnosticd and the simulator folder.
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!