ReportCrash uses 100% CPU, creates ~7 systemstatsd logs per second
| Originator: | ide | ||
| Number: | rdar://17970319 | Date Originated: | 09-Aug-2014 |
| Status: | Open | Resolved: | |
| Product: | OS X | Product Version: | 10.10 DP5 (14A314h) |
| Classification: | Reproducible: |
After using Yosemite for awhile, ReportCrash consumes close to 100% CPU according to Activity Monitor. Looking at the Console, about 7 log files for systemstatsd are created per second. One of these log files is attached. After restarting the computer, ReportCrash no longer consumes a lot of CPU. Steps to Reproduce: 1. Use Yosemite for awhile. Apps used: Xcode 6, Chrome, Safari, Slack, Atom editor, Mail, Terminal. 2. Check Activity Monitor, see high CPU usage 3. Look at Console, expand System Diagnostic Reports 4. See new log entries for systemstatsd created at a high rate Expected Results: ReportCrash should not be consuming a lot of CPU Actual Results: Many systemstatsd logs are created by ReportCrash Version: Mac OS X 10.10 DP5 (14A314h) Configuration: MacBook Pro (Retina, 15-inch, Late 2013) CPU: 2.6 GHz Intel Core i7 Memory: 16 GB 1600 MHz DDR3 GPU: Intel Iris Pro 1536 MB Boot ROM Version: MBP112.0138.B02
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!