Timeline for Suddenly the "diagnosticd" daemon rise up to over 200% CPU usage
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 16 at 21:46 | vote | accept | Pasquale Simonetti | ||
| Aug 28, 2022 at 19:18 | comment | added | Kendall Helmstetter Gelner | This also solved my problem, very odd that having a simulator just open (not even running an app) would cause diagnosticd to go wild and chew CPU... must be related to logging overload like other responses mentioned. | |
| Aug 22, 2022 at 11:27 | comment | added | Dylan Hand | For me quitting the simulator wasn't enough - I had to quit Xcode as well. | |
| Dec 2, 2021 at 8:49 | comment | added | de. | Normally it does not use that much CPU. I don't know how it gets into this state. You can try "Device" > "Erase all Content and Settings..." from the menu or just use another simulator. For me the issue eventually went away before the pain got high enough to do more debugging. | |
| Dec 1, 2021 at 23:12 | comment | added | Don Branson | It's amazing how much CPU the simulator uses when there's absolutely nothing going on. | |
| Feb 14, 2021 at 22:21 | history | edited | de. | CC BY-SA 4.0 |
deleted 5 characters in body
|
| Aug 17, 2020 at 14:46 | review | Low quality posts | |||
| Aug 17, 2020 at 17:01 | |||||
| Aug 17, 2020 at 14:31 | history | answered | de. | CC BY-SA 4.0 |