CPU usage is high #9358

Activity

1. natsuboy

   added

   bugSomething isn't workingSomething isn't working

   on Jan 19, 2026
2. github-actions

   assigned

   rekram1-node

   on Jan 19, 2026
3. github-actions

   added

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

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

   

   github-actionsBot

   on Jan 19, 2026 – with GitHub Actions

   Contributor

   More actions

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

   • High CPU Utilization Due To Repeated Git Process Invocations #9059: High CPU Utilization Due To Repeated Git Process Invocations - OpenCode makes thousands of 'git show' calls in a loop causing very high CPU usage
   • High CPU usage (100%+) during LLM streaming in long sessions due to O(n) text buffer rendering #6172: High CPU usage (100%+) during LLM streaming in long sessions due to O(n) text buffer rendering - Detailed analysis of CPU spikes reaching 100-117% sustained during streaming
   • [BUG] Snapshot module ignores 'watcher.ignore' config, causing excessive disk usage and performance degradation #8887: [BUG] Snapshot module ignores 'watcher.ignore' config, causing excessive disk usage and performance degradation - Git add processes cause high CPU and I/O during every agent step
   • Glob search uses 100% of CPU #5220: Glob search uses 100% of CPU - ripgrep/glob operations consume 100% CPU
   • perf: ripgrep config file search scans entire home directory including large hidden directories #6741: perf: ripgrep config file search scans entire home directory including large hidden directories - Causes 1000%+ CPU on home directory scans

   Feel free to ignore if none of these address your specific case.
5. github-actions commented on Mar 27, 2026

   

   github-actionsBot

   on Mar 27, 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.
6. github-actions

   closed this as completedon Mar 27, 2026