Skip to content

fix: roll sub-process MEM/CPU up over the subtree it spawned - #67

Merged
stefanprodan merged 1 commit into
mainfrom
subproc-usage-rollup
Oct 1, 2026
Merged

stefanprodan merged 1 commit into
mainfrom
subproc-usage-rollup

Conversation

@stefanprodan

Copy link
Copy Markdown
Owner

Sub-process rows showed only the RSS and CPU of the displayed process. A launcher like kiro-cli, whose work runs in the processes it starts (kiro-cli-chat → kiro-cli-chat acp), read about 30M instead of about 360M. Copilot, npm run dev, and similar launchers were under-reported the same way.

  • A row's MEM and %CPU are now totals for the displayed process and everything it spawned. This is the same subtree the ports column already uses, and it stops at nested Claude sessions, which have their own rows.
  • Every pid in those subtrees is now sampled on each refresh, so the CPU deltas stay live.
  • Sub-process rows sort by the total memory.

Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
@stefanprodan
stefanprodan merged commit 54d2e9e into main Oct 1, 2026
2 checks passed
@stefanprodan
stefanprodan deleted the subproc-usage-rollup branch October 1, 2026 17:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant