MBP Early 2011 on DP 4. About four hours after each boot, a process called "systemstats" starts to use an insane amount of resources - 4.1 GB of my 8 GB as well as 100% of CPU. Evidently this is the process that collects power usage data, and I am forced to force quit it in Activity Monitor to have a usable computer again. Did anyone else have this problem or know how to fix it? Thanks.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Process "systemstats" is wasting resources
- Thread starter pianoplayer98
- Start date
- Sort by reaction score
Sorry I have no idea. It is behaving normally on my system. Other than the usual file a bug report, I have no other ideas.
There is one thread on the developer forums
https://devforums.apple.com/message/827251#827251
They don't have any suggestions other than file a report.
Reboot, reset PRAM and SMC.
Also try force quitting the process, it might reload and run properly afterward.
Also try force quitting the process, it might reload and run properly afterward.
Yes. This just happened to me just now. That's why i came to this forum thread.
WTF is with this thing? When i force quit it, the CPU and memory amount decreased a lot, but the process did NOT disappear. i cannot actually get it to really be killed.
So they created a new system service to check what system resources are being used and wasted by software, and it wastes massive amounts of resources. WTF? It got so bad that my fans went full speed, the machine heated up, and the CPU use was over 150% and the entire system wasn't being responsive.
----------
https://discussions.apple.com/message/23720771#23720771
WTF is with this thing? When i force quit it, the CPU and memory amount decreased a lot, but the process did NOT disappear. i cannot actually get it to really be killed.
So they created a new system service to check what system resources are being used and wasted by software, and it wastes massive amounts of resources. WTF? It got so bad that my fans went full speed, the machine heated up, and the CPU use was over 150% and the entire system wasn't being responsive.
----------
https://discussions.apple.com/message/23720771#23720771
Question for all of you having this problem: did you have a new Mac volume being indexed at the time? i do/did. i found mds and its assorted services using a lot of resources. Looked it up and found that it is the indexing service. Sure enough, i had plugged in my old MacBook Pro 3,1 hard drive via external USB drive enclosure, and instead of importing the index from that drive, it's just indexing it all over again on the main machine. i don't know if there's a relationship, but i though i would mention it in case anyone else noticed the same.
I'd leave your machine on for a night or so, turning off powersavings. Let the process run its job for a bit and see if it returns.
Thanks by the reply =)
I've followed that guide, and this other http://gigaom.com/2011/07/26/when-to-reset-your-macs-pram-and-smc/ and managed to reset PRAM and SMC.
Works like a charm \o/ problem solved.
Thanks a lot.
I've followed that guide, and this other http://gigaom.com/2011/07/26/when-to-reset-your-macs-pram-and-smc/ and managed to reset PRAM and SMC.
Works like a charm \o/ problem solved.
Thanks a lot.
The systemstats process maintains a database in the folder /private/var/db/systemstat.
Perhaps it's corrupted; you could try killing systemstat, removing that database (or better rename it) and reboot.
Perhaps it's corrupted; you could try killing systemstat, removing that database (or better rename it) and reboot.
If I had to guess, the .stats files are one-time snapshots captures of resource use (resources being memory, CPU, disk usage). And the snapshots.db is probably the database, the aggregation of the .stats files.
I'd just stop the process and then rename the folder itself. That way, after a reboot everything will be recreated, I'd hazard to guess.
Run TimeMachine before doing so
I'd just stop the process and then rename the folder itself. That way, after a reboot everything will be recreated, I'd hazard to guess.
Run TimeMachine before doing so
If I had to guess, the .stats files are one-time snapshots captures of resource use (resources being memory, CPU, disk usage). And the snapshots.db is probably the database, the aggregation of the .stats files.
I'd just stop the process and then rename the folder itself. That way, after a reboot everything will be recreated, I'd hazard to guess.
Run TimeMachine before doing so
I know this thread is a little old, but it did help me and I would like to recognize that help.
I ran across this thread looking for a solution to a runaway systemstats process on my Mavericks server. I had found that killing the process worked, but only temporarily. This seem’s to be more of a permanent solution. Since I did this the systemstats process is behaving itself, I am still keeping an eye on things, but so far so good.
Thank you for your suggestion.
Edit: The above fix lasted for about 3 weeks.
Edit #2: Make sure that the folder is not available and the process cannot work. If you reboot, the folder will be re-created, immediately go and find the folder and rename it. This seems to be working……….Feb 02/17
Edit #3: Still working great..........Mar 28/17
Edit #4: Oct 23/17, server has now been "up" for 314 days without a problem
Last edited: