Memory leak: --claude-in-chrome-mcp processes accumulate without cleanup

Summary

--claude-in-chrome-mcp processes spawn continuously (~4/minute) when a browser session exists, without cleanup. Over ~10 hours, this accumulated 189 processes consuming 27GB RAM.

Environment

• Claude Code: 2.0.76
• macOS: Darwin 25.3.0 (arm64)
• RAM: 48GB

Reproduction

1. Use browser automation tools (mcp__claude-in-chrome__*)
2. Complete work but don't explicitly close browser (normal usage)
3. MCP processes spawn every ~15 seconds on a polling loop
4. Processes never cleaned up, memory grows unbounded

Timeline observed:

16:30 - dev-browser opened for dashboard testing
~03:00 (next day) - 189 MCP processes, 27GB consumed

Spawn pattern (after killing processes, they immediately resumed):

02:56:42 → 02:56:57 → 02:57:12 → 02:57:28 ...

Expected Behavior

• MCP connections should be reused, not spawn new processes per poll
• Process pool with max limit and recycling
• Cleanup mechanism when browser closes or goes stale
• Graceful handling of long-running browser sessions

Workaround

pkill -f "claude-in-chrome-mcp"
pkill -f "Google Chrome for Testing"  # kill stale Playwright browser

Impact

• System memory exhaustion on normal usage patterns
• Required manual intervention to recover
• Affects users who work with browser tools across multiple sessions