High CPU usage while waiting for limit reset #40649

Activity

1. github-actions

   assigned

   simonklee

   on Aug 5, 2026
2. github-actions commented on Aug 5, 2026

   

   github-actionsBot

   on Aug 5, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • [Bug]: Session processor retries indefinitely with unbounded exponential backoff — no max retries or circuit breaker #17648: Session processor retries indefinitely with unbounded exponential backoff — the infinite retry loop likely explains the sustained CPU usage you're observing during rate limit waits
   • fix(session): SessionRetry.policy() retries forever with no max attempt count #21960: SessionRetry.policy() retries forever with no max attempt count — same root cause from a different angle
   • High CPU usage in newer versions of OpenCode #30086: High CPU usage in newer versions of OpenCode — general high CPU reports that may share the same underlying cause
   • opencode is using CPU for doing nothing! #19466: opencode is using CPU for doing nothing — CPU consumption while idle/waiting, similar symptom

   If your issue is specifically about CPU burning during the retry countdown (rather than a general regression), #17648 and #21960 are the closest matches.

   👎React with 👎1Reacted by Fabian Schneider
3. Fabian123333 commented on Aug 5, 2026

   

   Fabian123333

   on Aug 5, 2026

   Last edited by Fabian123333

   Author

   More actions

   

   #13817 is similar, but not completely related. This is about the refresh rate of the RDP Session, it does not mention a high CPU rate of the other opencode processes. The suggested topics are after reading them carefully not really covering the case.

   I reopened the case, as a local low CPU load should be normal
4. Fabian123333

   closed this as a duplicateof [FEATURE]: limit the FPS (frames per second) target rate, useful for remote work #13817 on Aug 5, 2026
5. Fabian123333

   reopened this on Aug 5, 2026
6. github-actions commented on Oct 6, 2026

   

   github-actionsBot

   on Oct 6, 2026 – with GitHub Actions

   Contributor

   More actions

   To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
7. github-actions

   closed this as not plannedon Oct 6, 2026