Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Constant CPU usage on macOS 10.15.5
See original GitHub issue- I have searched the issues of this repo and believe that this is not a duplicate.
- I have searched the documentation and believe that my question is not covered.
Issue
I’ve just started using ActivityWatch on macOS 10.15.5. I’ve noticed that when AW runs, the process “System-Events” continuously uses ~15% CPU on my MacBook Pro 13" 2015 (see screenshot), and even leads to the fans constantly spinning quite audibly in clamshell mode.
Disabling aw-watcher-window made the CPU usage drop to almost zero.
Is this normal behavior? Is there anything I can do to reduce the CPU usage but still track my usage?
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
How to Fix High CPU Usage on macOS 10.15 Catalina
Sometimes, when macOS 10.15 receives updates, especially security updates, it may result in high CPU usage. This update not only slows down your...
Read more >OS X 10.15 and High CPU Usage for bsdtar
I have 10.15 installed on a test computer, a Mac Mini and when I boot up, three (3) bsdtar process start up and...
Read more >5 Ways to Fix High CPU Usage on macOS
5 Ways to Fix High CPU Usage on macOS · 1. Update Software and Restart Your Mac · 2. Use Activity Monitor to...
Read more >Accountsd: How to Fix High CPU Usage on Mac
Following the release of macOS Catalina version 10.15.7, an increasing number of users have experienced an issue with a system process named ...
Read more >High CPU Usage on macOS Catalina.... This is very ...
It is a known issue that OneDrive sometimes use too high CPU usage and memory in Mac OS, per the threads from OneDrive...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The thing is that this is very hard for us to know because it’s not ActivityWatch itself taking up the CPU resources but a macOS process which is not open source.
The only thing I know is that our way of getting the focused window with aw-watcher-window only asks for the focused window, whether macOS internally needs to iterate over all windows to find that however we can’t know.
As stated in the other PR though there’s a PR to rewrite the whole macOS backend for aw-watcher-window which hopefully will make things more reliable, I think that’s our best shot at improving/fixing this. https://github.com/ActivityWatch/aw-watcher-window/pull/40
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.