Describe the bug
I'm finding that every once in a while my home assistant (hass process) goes to 100% and stays pegged there until the service is restarted.
To Reproduce
Unfortunately, it has taken a long time to debug because it's extremely intermittent, and the only symptom is the 100% cpu usage (which is reflected in things like periodic checks getting delayed, and slow responses to events). There are no obvious log entries, so the only thing I can do is disable various integrations and run for a few weeks to see what happens. After a restart it can take several days to a week or more before the problem occurs. But I'm pretty well convinced the the problem is somehow related to the openepaperlink integration. I've been running for more than three weeks with the integration disabled (the only one that is disabled) and have not seen the problem.
Expected behavior
Under normal circumstances, CPU usage rarely goes over 30%, and then only briefly.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
I'm still not 100% certain the openepaperlink integration is the problem, or what I might be doing to trigger it. My main motivation for filing the bug report is to get it on record, and see if anyone else has seen a similar problem.
I'm happy to run any tests that would help, but keep in mind that it can take up to week to have reasonable confidence that
the problem is not happening.
Describe the bug I'm finding that every once in a while my home assistant (hass process) goes to 100% and stays pegged there until the service is restarted.
To Reproduce Unfortunately, it has taken a long time to debug because it's extremely intermittent, and the only symptom is the 100% cpu usage (which is reflected in things like periodic checks getting delayed, and slow responses to events). There are no obvious log entries, so the only thing I can do is disable various integrations and run for a few weeks to see what happens. After a restart it can take several days to a week or more before the problem occurs. But I'm pretty well convinced the the problem is somehow related to the openepaperlink integration. I've been running for more than three weeks with the integration disabled (the only one that is disabled) and have not seen the problem.
Expected behavior Under normal circumstances, CPU usage rarely goes over 30%, and then only briefly.
Screenshots If applicable, add screenshots to help explain your problem.
Additional context I'm still not 100% certain the openepaperlink integration is the problem, or what I might be doing to trigger it. My main motivation for filing the bug report is to get it on record, and see if anyone else has seen a similar problem.
I'm happy to run any tests that would help, but keep in mind that it can take up to week to have reasonable confidence that the problem is not happening.