Memory Usage and Leak Investigation
Diagnose growing memory in a service.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Help me find a memory problem by interviewing me first. Ask one question at a time and wait: (1) the language, runtime, and version, (2) how the process runs (container, server, serverless, browser), (3) how memory grows over time and what a graph looks like, (4) what changed shortly before it started, (5) whether memory returns after a restart or traffic drop, (6) whether it happens in all environments, and (7) what tools I have used (heap snapshots, profilers, metrics). What I know so far: [SYMPTOMS]. After the interview, give me a ranked list of the five most likely causes for my stack (for example unbounded caches, listeners never removed, global collections, large buffers, connection pools, closures holding references), each with the evidence that would confirm or reject it. Then give a step-by-step investigation plan using my runtime's tools: how to take two heap snapshots at different times, what to compare, what a leak looks like in the output, and how to reproduce under load safely. Add a short-term mitigation (memory limits, restarts, alerts) and a prevention checklist. Be clear when you are guessing.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into ChatGPT, Gemini, Claude or another assistant.