How to measure a Next.js memory leak and prove the diagnosis

Originally published at xabierlameiro.com. Quick answer Most memory leak reports die in the same place. Someone posts a graph that climbs, a maintainer asks for heap snapshots taken after a forced GC, and nobody comes back. I don't think that's laziness — taking those snapshots correctly is harder than the thread makes it sound, and getting it...