Loading…
Debug a Service That Is OOM-Killed Every Few Hours is a medium troubleshooting interview question covering troubleshooting, memory leak, resource exhaustion, debugging, monitoring and alerting — the kind asked at FAANG (Facebook/Meta, Apple, Amazon, Netflix, Google) and AI-first companies like Anthropic, OpenAI, and Nvidia.
A service is being killed by the kernel for exceeding its memory limit every few hours. It restarts automatically and mostly works, so this has been happening for a week. Memory climbs steadily and keeps climbing overnight when traffic is very low. The container limit is 2 GB.
Interactive walkthrough on Pro
Upgrade to Pro to unlock the clarifying questions, the narrowing ladder, the likely causes with their fixes, follow-up answers, and the model answer.
What's inside this guide
Fully unlocked, no account needed — solutions, walkthroughs and follow-up answers included.
Or start the Study Plan — a week-by-week order for your loop, and week 1 is entirely free.
A full interview loop is more than one round. These are the others, each with what is on the site for it.