Environment:
- OS: Ubuntu Linux (kernel 6.14)
- Claude Code v2.1.150, VS Code extension (IDE mode)
- 2 projects open simultaneously, each with an active Claude Code session
Observed:
While working with 2 active Claude Code sessions in VS Code, the system became unresponsive (load average: 30+, ~85% CPU usage system-wide).
Inspecting running processes revealed 4 concurrent ccstatusline node processes consuming ~470% CPU combined:
171% npm exec ccstatusline@latest
111% npm exec ccstatusline@latest
98% npm exec ccstatusline@latest
90% node .../ccstatusline
Killing the processes and removing the ccstatusline extension resolved the slowdown.
Possible hypothesis:
The Stop hook fires npx -y ccstatusline@latest per session per response. With multiple concurrent sessions, this may multiply the number of spawned node processes linearly. However, I was unable to fully confirm this as the root cause — other factors (VS Code TypeScript server, Expo bundler) were also running at the time.
Environment:
Observed:
While working with 2 active Claude Code sessions in VS Code, the system became unresponsive (load average: 30+, ~85% CPU usage system-wide).
Inspecting running processes revealed 4 concurrent
ccstatuslinenode processes consuming ~470% CPU combined:Killing the processes and removing the ccstatusline extension resolved the slowdown.
Possible hypothesis:
The Stop hook fires
npx -y ccstatusline@latestper session per response. With multiple concurrent sessions, this may multiply the number of spawned node processes linearly. However, I was unable to fully confirm this as the root cause — other factors (VS Code TypeScript server, Expo bundler) were also running at the time.