I want to find memory leaks before my users' browsers and my server find them for me. Audit both sides: Client-side, look for: 1. Event listeners added but never removed when components unmount or elements are removed. 2. Timers (setInterval, setTimeout chains) that keep running after their UI is gone. 3. Subscriptions (websockets, observers, store subscriptions) without unsubscribe paths. 4. Closures holding references to large objects or detached DOM nodes. 5. Client-side caches or arrays that only ever grow (every fetched item appended forever). Server-side, look for: 1. Module-level Maps, arrays, or caches with no eviction policy. These are the classic Node leak: memory climbs until the process dies. 2. Event emitter listener buildup (listeners added per request on a long-lived emitter). 3. Unclosed resources: database cursors, file handles, HTTP streams without cleanup on error paths. 4. Per-request data attached to long-lived objects. For each finding, implement the fix: remove listeners on teardown, clear timers, add eviction or size caps to caches, close resources in finally blocks. Where possible, verify: a before/after measurement or a small stress script showing memory stabilizing instead of climbing. If my platform makes profiling hard, at minimum show me the code-level fixes with reasoning.