NextJS Memory Leak

[antoniofpereir]

Summary

Running nextjs (v14.2.3) in a docker instance causes memory leaks (heap dump examples below)

We already optimized the code as much as we could but taking heap snapshots from a local docker instance running a stress test shows an accumulation of the "(string)" mainly in "__ next_chunk_load__"(examples below) and upon opening them it's just values that we pass as props to multiple components (server side rendered)

Additional information

Operating System: node 18 alpine (18.20.3)
NextJS Version: 14.2.3

Example

No response

[chipcop106]

I have the same issues. Memory leak with NextJS 14.2.3 and node 18 alpine (18.20.3). Any one help?

[antoniofpereir]

I got some update, it turns out it was not a problem on NextJS side. We were performing a fetch request without using .json, .blob or .text, which prevents the request from closing and ends up lingering in memory, worth a check

[VIGDXX]

We were performing a fetch request without using .json, .blob or .text, which prevents the request from closing and ends up lingering in memory, worth a check. --- I'm having the same issue, but i can't understand the solution,can you show more details please?

[YutaMoriJP]

@VIGDXX I think what they're saying is that you must read the body:

This would leak in Node. So you have to read the body json/text, etc. If you just need the headers of the response, then you should just fetch the headers.

const res = await fetch();
if(!res.ok) {
throw new Error()
}

[LokeshParthiban]

I use Next v14.2.4 with node 18.x. I face similar memory leak issues in my server where nextjs is running inside docker. We do read all the fetch responses with .json() or .text(). But i still see the leak.

[abemelek]

I use Next v14.2.4 with node 18.x. I face similar memory leak issues in my server where nextjs is running inside docker. We do read all the fetch responses with .json() or .text(). But i still see the leak.

I had the same issue. What fixed it was bumping my docker base image to node:20-alpine3.21 from node:20-alpine3.18

[twoyoung04]

I use Next v14.2.4 with node 18.x. I face similar memory leak issues in my server where nextjs is running inside docker. We do read all the fetch responses with .json() or .text(). But i still see the leak.

I had the same issue. What fixed it was bumping my docker base image to node:20-alpine3.21 from node:20-alpine3.18

it works for me too