Hi,
I have the 2012 ivybridge mac book air. I upgraded my os to mavericks the day it was released. Everything seems to be running fine expect the all of a sudden, the CPU cooling fan will kick into high gear. When I check the activity monitor, the culprit seems to be "systemstats". Anyone else having an issue with this or know how to solve this problem?
Thanks,
Brian H.
MacBook Air (13-inch Mid 2012), OS X Mavericks (10.9), High CPU Usage
Hi,
Same problem with my Macbook Pro (13-inch, 2011).
Regards,
Gerald R
I have the same issue on mbp 15 mid 2012 after clean installation of 10.9. It starts to consume 100% of one core of CPU and more that 1Gb of RAM after some point. It is in the state "Collection Power Usage Information...". And I have 2 such processes
Here the same! I have a Macbook Pro 13" Mid 2010 and did a clean install of Mavericks. Activity monitor shows me systemstats which uses 80% of the CPU
Same problem here. Mac Mini Server 2010.
Ok so after reading up on another related problem "battery draining" issue that I also had. Resetting the SMC and PRAM seems to have solved the systemstats issue and a whole crap load of other minor bugs that were annoying me. You definitly want to give this a try: https://discussions.apple.com/docs/DOC-3604 also, this third party site's instructions seem a little more clearer than apple's http://gigaom.com/2011/07/26/when-to-reset-your-macs-pram-and-smc/
Do give restting these two items a try. For me, it as solved 99% of my problems.
Doesn't work for me, tried it both multiple times, but from time to time the fan speed is increasing and the cpu load high. The battery icon show always "Collecting information about energy consumption"
Same here. Macbook Pro 13" early 2011.
Had the same, just restarting my machine solved it
Using the MacBook Pro Retina 15" Late 2013.
Hi,
read this article on the same topic. Haven't tried it myself yet.
After cobbling together some things from the links in this thread, I was able to fix the problem on my machine by doing the following in the Terminal. If you aren't comfortable with the command line, be careful.
Step 4 is for safety. I actually just rm -rf'd the directory contents. Once you reboot everything should be working normally. For the first time I now see why people were impressed with the "Apps using significant energy" feature, since it actually works within seconds and doesn't send systemstats into a frenzy anymore. Hope this helps those who are still having the issue.
Commandline solution worked for me:
After restart everything worked as usual. The snapshots.db was automatically recreated. Now systemstats still goes up to 100% sometimes, but now only for a few seconds max.
The snapshots.db had a size of almost 600 Mb !!! I removed it after I restarted it (sudo rm BACKUP_snapshots.db).
If I now have a look at 'Apps using significant energy' then I see it immediately. Before it was very slow to react.
I think the original problem is caused by the size into which snapshots.db can grow. Just a few minutes after restart, the file snapshots.db was already at more then 100Kb again. So in a few months... Maybe good idea to have a regular look at...
This fixed it for me. Same thing the snapshots.db had grown to 300 MB, although i removed the entire folder. After reboot, the folder was recreated and system was behaving within norm again.
Wel ... after I had to kill a 'Safari Web Content' process as well. Curious thing was that that process came back after reboot, for as soon as I fired up my web browser, I recognized the URL as an old URL I visited, and not even displayed in the browser (no tabs or hidden windows as I used also expose to make sure there was no window off-screen).
The snapshots issue does seem to be like a bug, with a real old solution behind it (provided link goes back to 2011...). I Do hope that a developper can submit this as a traceble bugreport with Apple through an apple developer account?
That only temporarily solved the problem, might just as well to reboot. A few days later, same issue. I got curious and let systemstats run. It ran for about 10 minutes and stopped.
------------
Commandline solution worked for me:
What the hack! It seems systemstats is controlled by some cron daemon. On my macbook, it runs every day at round 12am using up 1 core for a few minutes. Tired of rebooting, I just move it to /usr/sbin/systemstats.bak . No adverse effect has been observed so far after a few reboot to test it out.
snapshots.db is a SQLite database and when it gets big you can vaccum it:
sudo sqlite3 /private/var/db/systemstats/snapshots.db vacuum
This will cleanup unused space in the file. I can't say for sure that this will solve the problem with the systemstats, but it's a little less heavy handed than deleting everything.
systemstats using high CPU after upgrade to Mavericks
