Closed martin-t closed 9 months ago
github-actions[bot]
commented
1 year ago Hi there! As you're new to this repo, please make sure you've used an appropriate issue template and searched for duplicates (it helps us focus on actual development!). We'd also like to suggest that you read our contribution guidelines and our code of conduct. Thanks a bunch for opening your first issue! 🙏
BelKed
commented
1 year ago Seems like a duplicate of https://github.com/ActivityWatch/aw-watcher-window/issues/89
martin-t
commented
1 year ago Possibly. I recall AW having high CPU usage on my other computer a few times but back then i didn't investigate and just restarted it. This time I thought it crashed but i haven't looked at CPU usage so maybe it's the same issue.
martin-t
commented
12 months ago Ok, it happened again, CPU usage on one core is 100% from the window watcher and the error is in logs again. I renamed the issue since it doesn't crash, it gets stuck.
digitalextremist
commented
9 months ago Not sure if duplicate of:
But seeing same behavior with v0.12.2
Pinning CPU at 100% ( noticed due to fan running and CPU heat reaching mid ~190F, which is >50-80F higher than normal )
ErikBjare
commented
9 months ago @digitalextremist Should be fixed in v0.12.3b10 as per https://github.com/ActivityWatch/aw-watcher-window/issues/89#issuecomment-1717129228.
martin-t
commented
9 months ago I don't think this is fixed. I downloaded v0.12.3-beta.10 yesterday and today it happened again.
I am assuming it's the same bug - aw-watcher-window had 100% CPU usage and there are no events recorded during the 20 minutes it took me to notice.
However i can't confirm it because there's no log file for today, not sure why, does the new version not write logs for some reason? Did that path change? The only component producing logs is aw-server-rust now; aw-qt, aw-watcher-afk and aw-watcher-window stopped.
ErikBjare
commented
9 months ago @martin-t Thanks for reporting!
Looks like the dependency wasn't properly updated due to a conflict with aw-watcher-afk also depending on python-xlib. Fixed in https://github.com/ActivityWatch/aw-watcher-afk/commit/2b638db86dd24000775bff260691fdb190e7c74a. Validating change in CI now.
And about the log files, I noticed they had been moved after a breaking change in one of our dependencies https://github.com/ActivityWatch/aw-core/pull/122. Fixed now.
Making a new release soon.
Describe the bug
The window watcher appears to have crashed - its row on the timeline view ends abruptly even though other watchers continue saving data. Logs contain
AttributeError: 'BadRRModeError' object has no attribute 'sequence_number'at the time when the timeline ends - attached below.EDIT 2023-07-28 It doesn't crash, it just gets stuck with 100% CPU usage.
To Reproduce
No idea what causes it, according to a different time tracker, i was working in vscode and konsole at the time of the crash and didn't do anything special. The same crash has happened 6 times over the past 4 months though.
Expected behavior
1) It shouldn't crash. 2) It should automatically restart itself unless the same error happens repeatedly.
Documentation
Logs from
~/.cache/activitywatch/log/aw-watcher-window/aw-watcher-window_2023-07-19T13-06-10.logI only edited out the middle where the same warning keeps repeating hundreds of times.