When memory errors suddenly started crashing our Node.js app, we knew something unusual was going on. This post shares how we tracked down the leak and what helped us solve it — from heap snapshots…

Trendyol Tech Blog offers a glimpse into the technology and engineering practices powering one of Turkey's leading e-commerce platforms. With a focus on scalability, performance, and innovation, Trendyol Tech shares insights into microservices architecture, data engineering, and machine learning. Developers can learn about building high-traffic e-commerce systems, optimizing delivery pipelines, and leveraging  technologies to drive business growth.

Trendyol Tech

An unexpected memory leak in a Node.js application was discovered during a code freeze, with symptoms including crashing services and unusual memory patterns. The issue was traced back to incorrect file permissions preventing log flushing to disk, causing logs to accumulate in memory. The team used tools like Chrome DevTools and heap snapshots to diagnose and resolve the leak, leading to stabilized memory usage and improved system stability.

Everything Looked Fine Until Memory Ran Out in Our Node.js App

When vibe coding doesn’t work and you can’t figure out why. Get good and don’t blame Node.

In our project also we got this issue, Thank You for sharing this will be helpful Bro

On the team I work on we currently have this issue but it’s not relating to file permissions and we have not been able to fully figure it out. I had to redo some logic so we can solve this problem