-
-
Notifications
You must be signed in to change notification settings - Fork 620
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aw-watcher-window 100% CPU #917
Comments
Could you please try to find the latest version that works for you — it doesn't have the bug? |
As far as I remember, this was also the case in previous versions. It would be hard for me to track down by installing the previous version because it doesn't always happen. I haven't observed a rule of when (other than usually after waking up from sleep). Possibly the fact that I'm working on multiple monitors has something to do with it? (I plug into a docking station where there are 2 additional monitors). |
Today however, without sleeping / waking up, I worked without the docking station, then without closing the laptop I plugged it into the docking station and after a while activitywatch warmed up the CPU, in htop again around 90% cpu. So maybe the docking station + external monitors is a clue after all? If I can send some helpful logs, please indicate which ones. I can also approach something at the time of the event itself if I get the right instructions. |
This might be a duplicate of #920 which has been resolved. |
I'm closing this, but if the issue occurs again, please do let us know. Thanks for reporting! ❤️ |
I think this problem still exists. Often when I hear loud fans, I check htop and there Activitywath CPU 100%. I think the rule here is waking up the laptop from sleep, that's when I mostly observe this problem. Restarting the activitywatch process helps.
Version: v0.12.2 (rust)
Ubuntu 22.04.2 LTS
Originally posted by @qcol in #486 (comment)
The text was updated successfully, but these errors were encountered: