-
-
Notifications
You must be signed in to change notification settings - Fork 119
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
[Question: Inkycal and high CPU-usage #347
Comments
Hi there and welcome to Inkycal. Thanks for opening this issue. As this is your first issue in this repository, please read through the contributing guidelines |
Hi @mattenz and thanks for opening this issue. I'm using the latest version of Inkycal (from yesterday) and even on my Zero W, I do not see any cpu-intensive task running there as the total load is less than 2% on average (see screenshot below); Can you please check the following:
My |
I think I'm using the latest version...currently 2.0.3. This has been happening a while though on a previous version and I thought updating it a few weeks back to 2.0.3 might solve it but unfortunately not. To answer your quesitons:
|
Describe the bug
After InkyCal has been running for a bit (sometimes hours, sometimes days), it seems to just stop refreshing after a while, however it looks like the Python process is still running under this scenario and consuming a lot of CPU (80-85%). At the moment I have to schedule reboots of the Pi to keep InkyCal refreshing reliably.
Screenshots
The logs of InkyCal show that its last recorded refresh was an hour later than what is shown on the display itself (in this case, the logs say 21:01 but the display shows 20:01 - no more log events are logged from that time tho):
Additional context
The Pi is running Bullseye. My config file is as below:
I can't see any other instances running:
The text was updated successfully, but these errors were encountered: