The site is broken right now, but I read this when it was first submitted some time ago.<p>Contrary to what the title would suggest, it's about finding a mundane JS memory leak in moment.js by attaching the chrome inspector to node. There's no out-of-the-ordinary tale here and there's certainly little mystery.<p>The article might be useful if you've never done it before and need some pointers.
Is anyone else getting a redirect loop when trying the link? At first I was thinking it had to do with my Firefox settings to force HTTPS but even just:<p>curl -L lukedeniston.com/memory-leak-mystery<p>> curl: (47) Maximum (50) redirects followed<p>isn't working.
>The NODE_OPTIONS were only applying to the yarn process, not the underlying Next.js server that was being invoked by yarn.<p>Doesn't make sense. All child processes should get that env var.