Debian 12 Daemon Memory Leak Leading to OOM Kills

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Service uptime degrades as kernel OOM killer terminates processes under memory exhaustion.

Environment & Reproduction

Long-running daemon with unbounded allocation patterns on Debian 12.

dmesg | grep -i oom

Root Cause Analysis

Application memory leak and missing service memory guardrails drive eventual host instability.

Quick Triage

Capture top memory consumers and leak growth rates by process.

ps aux --sort=-rss | head

Step-by-Step Diagnosis

Profile memory usage over time and inspect OOM victim selection data.

journalctl -k -n 200

Solution – Primary Fix

Deploy patched daemon build and enforce memory ceilings in unit config.

sudo systemctl edit daemon-name

Solution – Alternative Approaches

Use periodic controlled restarts as temporary containment during remediation.

Verification & Acceptance Criteria

Memory footprint stabilizes and no new OOM events occur.

systemctl status daemon-name

Rollback Plan

Revert daemon package and config overrides if patched build introduces regressions.

Prevention & Hardening

Add memory telemetry and automated canary checks before wide rollout.

Related Errors & Cross-Refs

Correlate with swap thrashing and service restart storms.

Related tutorial: View the step-by-step tutorial for debian-12.

View all debian-12 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Consult systemd resource control and Linux OOM internals documentation.