https://cassiobotaro.dev/en/tags/nodejs/Recent content in Nodejs on cassiobotaroHugoenSat, 25 Jul 2026 13:06:19 -0300https://cassiobotaro.dev/en/posts/detecting-a-memory-leak-in-nodejs/Wed, 01 Apr 2026 00:00:00 +0000https://cassiobotaro.dev/en/posts/detecting-a-memory-leak-in-nodejs/<p><img src="https://cassiobotaro.dev/images/leak.png" alt="Leak"></p> <p>I recently had to investigate a strange memory growth in a real project. The behavior did not show up in development, but it blew up under load. I put together a minimal example that reproduces the scenario. More important than memorizing the fix is understanding the process: if you know how to repeat this flow, you will be able to investigate similar problems with much more confidence.</p> <h2 id="the-symptom"> The symptom <a class="heading-link" href="#the-symptom"> <i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"></i> <span class="sr-only">Link to heading</span> </a> </h2> <p>The endpoint fetched data with Sequelize, enriched each item with external information and serialized everything into the response. The problem only showed up when running it repeatedly under load.</p>