How can I debug a Docker container memory leak when the OOM killer terminates it randomly overnight without leaving a clear stack trace?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
How can I debug a Docker container memory leak when the OOM killer terminates it randomly overnight without leaving a clear stack trace?
1 real search · 1 real-search pass
Docker documentation memory constraints docker stats cgroup v2 memory.events OOMKilled inspect containerGoogle ↗
OBSERVEDConsequence
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
ChatGPT real searches (1)
Classes come from the query-classifier (a local Laya model). 1 of 1 calls are low-confidence (under 50%) — hover a query in the table to see its confidence.
Searches and sources
ChatGPT1 real searches · gpt-6
Docker documentation memory constraints docker stats cgroup v2 memory.events OOMKilled inspect container Google ↗
- Resource constraints · docs.docker.com
- Runtime metrics · docs.docker.com
- Running containers · docs.docker.com