Process/memory leaks: orphaned processes and zombie subagents #101
Labels
No labels
good first issue
has-pr
help wanted
idea
priority
critical
priority
high
priority
low
priority
medium
status
blocked
status
in-progress
status
needs-review
status
ready
type
bug
type
docs
type
enhancement
type
feature
type
refactor
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
customable/claude-mem#101
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Origin
Upstream issues #701, #737, #740
Problem
Multiple related issues causing memory and process accumulation:
Symptoms
claudeprocesses visible in task managerExpected Behavior
Related
pkill -f "claude.*--resume"pkill -f "worker-service.cjs --daemon"Partial Fix: Orphaned Active Sessions
Found and fixed a bug in the stop hook:
Problem: The stop hook was calling
/api/hooks/summarizewhich only queued summarization but did NOT mark the session as completed. Sessions stayed in 'active' state indefinitely.Fix: Changed to call
/api/hooks/session/endwhich:Commit:
d995106Remaining issues (Claude Code bugs, not claude-mem):
Orphaned claude processes - This is a known Claude Code bug with subagents not terminating. Workaround:
pkill -f "claude.*--resume"Zombie subagents - Also a Claude Code issue. Related: https://github.com/anthropics/claude-code/issues/19045
These are upstream Claude Code bugs and cannot be fixed in claude-mem.
Status Update:
This is an upstream Claude Code issue, not a claude-mem plugin bug. The referenced issues (#701, #737, #740) are in the Claude Code repository itself.
Current Mitigations:
pkill -f "claude.*--resume"cleanup commandpkill -f "worker-service.cjs --daemon"Plugin-side improvements possible:
The core fix must come from Anthropic's Claude Code team. Keeping this issue open to track any plugin-side mitigations we can implement.