When Your Agent Slowly Eats All the Memory
Your agent gateway starts at 200 MB RSS. Seven minutes later it's at 660 MB. Half an hour in, 850 MB. An hour later, it's unresponsive. No crash. No error. Just... slowly getting fatter until someo...
Source: DEV Community
Your agent gateway starts at 200 MB RSS. Seven minutes later it's at 660 MB. Half an hour in, 850 MB. An hour later, it's unresponsive. No crash. No error. Just... slowly getting fatter until someone mercy-kills it. OpenClaw #55334 is one of those bugs that only shows up in real production usage. The Setup 22 skills loaded, 12 cron jobs, frequent sub-agent spawns. The gateway maintains sessions.json tracking all sessions. Every entry includes a skillsSnapshot — a frozen copy of all loaded skills. Three Things Go Wrong 1. Ephemeral sessions never get pruned. Sub-agent and cron sessions complete but stay in sessions.json forever. 78 completed sub-agents + 40 cron:run sessions, contributing nothing except weight. 2. Every session duplicates the entire skill set. That skillsSnapshot is 41 KB per session. Across 188 sessions: 6.4 MB of duplicated skill definitions. 3. Orphan transcripts pile up. 153 orphan .jsonl files (36.4 MB) with no matching session, each triggering a warning on restart
