How to Fix OpenClaw High Memory Usage

# Find OpenClaw process memory:
top -b -n 1 | grep openclaw
# Or use htop for real-time monitoring:
htop -p $(pgrep -f openclaw)

# Get detailed memory breakdown:
cat /proc/$(pgrep -f openclaw)/status | grep -E "VmSize|VmRSS|VmSwap"
# VmRSS = actual physical RAM used

# Enable memory profiling in OpenClaw config:
export OPENCLAW_PROFILE_MEMORY=true

# Check skill memory usage in logs:
grep "memory_usage" ~/.openclaw/logs/openclaw.log

# For Node.js-based OpenClaw:
node --inspect --expose-gc ./openclaw.js
# Then use Chrome DevTools memory profiler

# For systemd services:
sudo systemctl edit openclaw
# Add:
[Service]
MemoryMax=2G
MemoryHigh=1.8G

# For Docker:
docker run -m 2g --memory-swap 2g openclaw/openclaw

# For Node.js processes:
node --max-old-space-size=2048 ./openclaw.js

# Edit OpenClaw config (config.json or .env):
MAX_CONTEXT_LENGTH=4000  # Reduce from default 16000
CONVERSATION_HISTORY_LIMIT=50  # Keep only last 50 turns
ENABLE_CONTEXT_COMPACTION=true

# Enable automatic summarization:
CONTEXT_SUMMARIZATION_THRESHOLD=8000
SUMMARIZATION_MODEL=claude-3-haiku  # Faster, cheaper

# List currently loaded skills:
curl http://localhost:3000/api/skills | jq .

# Disable unused skills in config:
DISABLED_SKILLS=skill-image-gen,skill-video-analysis

# Configure cache limits:
SKILL_CACHE_MAX_SIZE=100  # Max cached skill results
EMBEDDING_CACHE_TTL=3600  # Evict after 1 hour
CLEAR_CACHES_ON_RESTART=true

# Simple memory monitoring script:
cat > monitor-memory.sh << 'EOF'
#!/bin/bash
while true; do
  MEM=$(ps -o rss= -p $(pgrep -f openclaw))
  echo "$(date): ${MEM}KB"
  if [ "$MEM" -gt 2000000 ]; then
    echo "WARNING: Memory exceeds 2GB!" | mail -s "OpenClaw Memory Alert" admin@example.com
  fi
  sleep 300
done
EOF
chmod +x monitor-memory.sh

# Or use systemd with monitoring:
systemctl status openclaw | grep Memory