🐛 [CRITICAL] Workspace VM Service Crash + Memory Leak: 18+ Processes, 2.5GB RAM, Complete Freeze

Summary

Claude Code extension fails to start workspace with "VM service not running" error.
Spawns 18+ processes simultaneously, consuming 1.1GB+ RAM → complete system freeze.
Native memory leak confirmed via Node.js debugger and Task Manager.

Reproduction Steps

1. Install Claude Code (tested: 2.1.198, 2.1.211, 2.1.212 — ALL affected)
2. Open Cowork workspace
3. Observe: error "Failed to start Claude's workspace - VM service not running"
4. Task Manager: 18+ VS Code processes spawn simultaneously
5. System becomes unresponsive (freeze)

Expected Behavior

• Workspace starts normally
• Single process or controlled process pool
• Memory remains stable

Actual Behavior

• Workspace fails to start
• 18 VS Code processes spawned simultaneously
• RAM consumption: 1,163.6 MB (example: 207.7 MB, 255.8 MB, 140.6 MB, 82.4 MB per process)
• System freeze / unresponsiveness
• Error: "VM service not running. The service failed to start."

Root Cause (Debugged)

Native addon memory leak — STRUCTURAL BUG:

• Module: windows-mutex / child_process native addons
• Heap snapshot shows external memory not releasing: 6,624,217 bytes (6.3 MB)
• Heap: 15,743,164 bytes used (15 MB)
• RSS: 248,709,120 bytes (237 MB)
• Growth rate unsustainable

Critical Finding: Version-Independent

Problem persists across ALL tested versions:

• ✗ 2.1.198 — 18 processes, 1.1GB RAM
• ✗ 2.1.211 — 18 processes, 2.5GB RAM
• ✗ 2.1.212 — 18 processes, 2.5GB RAM

Conclusion: Bug is NOT version-specific regression. This is a structural/architectural issue in native addon management, not fixable by downgrade.

Troubleshooting Attempted

✅ Cleaned settings.local.json (200+ rules → 15 wildcards)
✅ Downgraded extension (2.1.212 → 2.1.211 → 2.1.198) — issue persists
✅ Full VS Code uninstall + Windows registry cleanup
✅ Cowork workspace complete reinstall
✅ Node.js debugger attached — confirmed native memory leak
✅ Heap profiling — external memory not released
✅ Task Manager monitoring — confirmed 18-process spawn across all versions

Timeline

• 2026-07-17 11:48 AM — Extension crash: "chatParticipant must be declared in package.json"
• 2026-07-17 12:15 PM — 18 processes spawn, full freeze
• 2026-07-17 12:30 PM — Attempted full uninstall/reinstall
• 2026-07-17 1:00 PM — Cowork workspace reinstall
• 2026-07-17 1:15 PM — In-app support ticket submitted
• 2026-07-17 1:30 PM — Multiple version downgrade tests (2.1.212 → 2.1.198) — all affected
• 2026-07-17 1:45 PM — Confirmed bug is structural, not version-specific

System Information

• OS: Windows 11 Home 10.0.26200
• Cowork Version: 1.22209.0
• Node.js: 24.18.0
• Electron: 42.6.0
• Claude Code Extensions Tested: 2.1.198, 2.1.211, 2.1.212 (ALL affected)
• Subscription: PRO
• RAM Available: 16 GB

Impact

• 🔴 CRITICAL — Active project blocked (ULC Due Diligence system, deadline at risk)
• 4+ hours lost to troubleshooting
• PRO subscription unusable
• Cannot use Claude Code in VS Code or Cowork
• Workaround: Using Claude CLI (functional, but limits VS Code integration)

Evidence

• Task Manager snapshot: 18 processes, 1.1GB+ RAM (provided in attached screenshot)
• Node.js heap snapshot available upon request
• Error logs available upon request

Email: tolstoistudio@gmail.com

---

NOTE: This is a STRUCTURAL BUG in native addon lifecycle management. Requires engineering review of windows-mutex / child_process addon release/cleanup cycle.