High CPU usage (100% single core) during TUI rendering #11119

Activity

1. alibert99

   added

   bugSomething isn't workingSomething isn't working

   on Jan 29, 2026
2. github-actions

   assigned

   rekram1-node

   on Jan 29, 2026
3. github-actions

   added

   opentuiThis relates to changes in v1.0, now that opencode uses opentuiThis relates to changes in v1.0, now that opencode uses opentui

   perfIndicates a performance issue or need for optimizationIndicates a performance issue or need for optimization

   on Jan 29, 2026
4. github-actions commented on Jan 29, 2026

   

   github-actionsBot

   on Jan 29, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • TUI rendering glitches: overlapping panels, misaligned content, and corrupted layout #11109: TUI rendering glitches: overlapping panels, misaligned content, and corrupted layout (related TUI rendering issues that may be caused by the same busy-loop)
   • OpenCode VS Code Extension: Great UI but severe lag on scroll translation + no pagination scrollbar #11115: OpenCode VS Code Extension: Great UI but severe lag on scroll translation + no pagination scrollbar (performance/lag related issue)
   • bug: apply_patch waits for LSPs sequentially causing big multi-file patches to hang #10965: bug: apply_patch waits for LSPs sequentially causing big multi-file patches to hang (related performance/blocking issue in TUI)

   Feel free to ignore if none of these address your specific case.
5. alibert99 commented on Jan 29, 2026

   

   alibert99

   on Jan 29, 2026

   Author

   More actions

   I confirm high CPU usage (100% one core) related to TUI. strace shows a busy loop on timerfd reads by the Worker thread.

   👍React with 👍7Reacted by Junyi Hou, Steven Lu, deflax, Azarattum, Barry Wang, xuyangyuio and Jebearssica
6. Junyi-99 commented on Jan 29, 2026

   

   Junyi-99

   on Jan 29, 2026

   Last edited by Junyi-99

   More actions

   same here, the iTerm2 is using 45% CPUs when opencode is running

   

   When opencode is not running, the CPU usage backs to 4.2%

   

   However, when I switch to Ghostty, the cpu usage drops down to 9.8%

   
7. unphased commented on Jan 30, 2026

   

   unphased

   on Jan 30, 2026

   Last edited by unphased

   More actions

   

   Something is definitely going on here.

   Nevermind, I think these are from stale dead tmux split instances from oh-my-opencode v3.1.2
8. github-actions commented on Apr 1, 2026

   

   github-actionsBot

   on Apr 1, 2026 – with GitHub Actions

   Contributor

   More actions

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

   closed this as completedon Apr 1, 2026