-
-
Notifications
You must be signed in to change notification settings - Fork 587
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 regularly gets stuck in an infinite loop #920
Comments
Hi there! |
Seems like a duplicate of ActivityWatch/aw-watcher-window#89 |
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. |
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. |
Not sure if duplicate of:
But seeing same behavior with Pinning CPU at 100% ( noticed due to fan running and CPU heat reaching mid ~190F, which is >50-80F higher than normal ) |
@digitalextremist Should be fixed in v0.12.3b10 as per ActivityWatch/aw-watcher-window#89 (comment). |
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. |
@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 ActivityWatch/aw-watcher-afk@2b638db. 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 ActivityWatch/aw-core#122. Fixed now. Making a new release soon. |
I am on the latest ActivityWatch version.
I have searched the issues of this repo and believe that this is not a duplicate.
OS name and version: Kubuntu 22.04
ActivityWatch version: v0.12.2 (rust)
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
Documentation
Logs from
~/.cache/activitywatch/log/aw-watcher-window/aw-watcher-window_2023-07-19T13-06-10.log
I only edited out the middle where the same warning keeps repeating hundreds of times.
The text was updated successfully, but these errors were encountered: