Describe the bug
When I open copilot TUI, it hogs one CPU (~6-7% on a 16 core machine).
After I run a prompt, that number multiplies to e.g. 2, 3 or 4 CPUs hogged while the TUI sits idle.
Affected version
GitHub Copilot CLI 1.0.83.
Steps to reproduce the behavior
- start copilot TUI, observe CPU usage (sometimes i need to type a bit in the prompt box for the issue to appear)
- run a prompt or two, observe CPU usage
Expected behavior
copilot TUI CPU usage is negligible while the program sits idle.
Additional context
Ubuntu 24.04, x86_64, GitHub Copilot CLI 1.0.83..
Logs below. I opened a session, typed in the prompt box (already 1 CPU hogged at that point), then gave a plan command. after the plan.md was written and the TUI was idle, it used 3-4 CPUs.
process-1788769402724-57168.tar.gz
Describe the bug
When I open copilot TUI, it hogs one CPU (~6-7% on a 16 core machine).
After I run a prompt, that number multiplies to e.g. 2, 3 or 4 CPUs hogged while the TUI sits idle.
Affected version
GitHub Copilot CLI 1.0.83.
Steps to reproduce the behavior
Expected behavior
copilot TUI CPU usage is negligible while the program sits idle.
Additional context
Ubuntu 24.04, x86_64,
GitHub Copilot CLI 1.0.83..Logs below. I opened a session, typed in the prompt box (already 1 CPU hogged at that point), then gave a plan command. after the plan.md was written and the TUI was idle, it used 3-4 CPUs.
process-1788769402724-57168.tar.gz