Closed qcol closed 8 months ago
Could you please try to find the latest version that works for you — it doesn't have the bug? If it's fixed in some of the older versions, it would help us narrow down the cause of the problem :)
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 https://github.com/ActivityWatch/activitywatch/issues/920 which has been resolved.
I'm closing this, but if the issue occurs again, please do let us know.
Thanks for reporting! :heart:
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 https://github.com/ActivityWatch/activitywatch/issues/486#issuecomment-1623184174