claude-code - 💡(How to fix) Fix [Windows Desktop] Frequent crashes, orphaned dev server processes, and zombie git processes after v1.2581.0 update [1 comments, 2 participants]

Summary

After updating to Claude Code v1.2581.0 (Windows Desktop App), the application crashes and restarts unexpectedly during routine development work — especially when starting or interacting with dev servers via preview_start. Previous server instances are not properly terminated on crash, making subsequent server starts fail with port-already-in-use errors. Additionally, orphaned git/git-for-windows/TortoiseGit processes accumulate (many in suspended state), causing severe system slowdown over time.

Environment

• Claude Code version: 1.2581.0 (Desktop App)
• Platform: Windows 11 Pro (Build 10.0.26200), AMD64
• Shell: bash (Git Bash / msys2)
• Model in use: Claude Opus 4.6 (1M context)

Project context

Full-stack TypeScript monorepo (npm workspaces):

• Frontend: Next.js app (apps/site, port 5200)
• Backend APIs: Express-based services (apps/api-web port 5201, apps/api-anthropic port 5203)
• Dev servers managed via .claude/launch.json and preview_start tool
• Typical workflow: iterative frontend development with frequent code edits, preview screenshots, snapshot checks, console/network inspection

Bug description

1. Frequent crashes and restarts

During normal development (editing files, running preview tools, reading code), the Claude Code desktop app crashes and restarts without warning. This happens significantly more often than before the v1.2581.0 update — roughly every 15–30 minutes of active use, sometimes more frequently.

No specific action consistently triggers the crash, but it often occurs:

• When starting a dev server via preview_start
• During heavy tool usage (multiple parallel tool calls)
• When the conversation context grows large

2. Orphaned dev server processes (port conflicts)

When the app crashes, dev server processes started via preview_start are NOT terminated. On restart, attempting to start the server again fails because the port is already in use by the orphaned process from the crashed session.

Expected behavior: On crash or restart, all child processes (dev servers) spawned by the previous session should be cleaned up, or preview_start should detect and kill stale processes on the same port.

Actual behavior: The orphaned node/next-server process holds the port. The user must manually find and kill the process via Task Manager before preview_start works again.

3. Zombie git processes causing system slowdown

After prolonged use (and multiple crash/restart cycles), Task Manager shows numerous git-related processes accumulating:

• git.exe (multiple instances)
• Git for Windows processes
• TortoiseGit helper processes
• Several of these are in Suspended state

These zombie processes are never cleaned up and cause severe system slowdown over time, eventually degrading the entire machine's performance. The only remedy is manually killing them or restarting the computer.

Steps to reproduce

1. Open Claude Code Desktop v1.2581.0 on Windows 11
2. Open a monorepo project with .claude/launch.json configured
3. Start a dev server via preview_start
4. Perform iterative development (edit files, use preview tools, read files)
5. Wait for crash (typically within 15–30 min of active use)
6. After restart, try preview_start again — fails with port conflict
7. Check Task Manager — orphaned node processes and suspended git processes visible
8. Repeat cycle — git processes accumulate, system slows down progressively

Expected behavior

• The app should not crash during normal development workflows
• On crash/restart, child processes (dev servers) should be cleaned up
• Git processes should not accumulate in suspended state
• System performance should not degrade over extended use

Actual behavior

• Frequent unexpected crashes and restarts
• Dev server processes survive crashes and block port reuse
• Git processes accumulate as zombies, many suspended
• System becomes progressively slower, requiring manual process cleanup

Workarounds

• Manually kill orphaned node/next processes via Task Manager before restarting dev servers
• Periodically check Task Manager for suspended git processes and kill them
• Restart computer when system becomes too slow

Additional context

• This regression started with v1.2581.0 — previous versions were significantly more stable on the same hardware and project
• The project uses Git Bash (msys2) as the shell environment
• .claude/launch.json uses npm run dev to start Next.js and Express servers