10.0.8 next/image high memory use

[scttcper]

What version of Next.js are you using?

10.0.8

What version of Node.js are you using?

14.15.4

What browser are you using?

chrome

What operating system are you using?

macOS

How are you deploying your application?

next start

Describe the Bug

With v10.0.8 on pages with lots of next/image components seeing much higher memory use compared to 10.0.7. Possibly related to #22253

Expected Behavior

less memory use

To Reproduce

checkout branch nextjs-leak https://github.com/scttcper/xmplaylist/tree/nextjs-leak
run yarn && yarn build && cd frontend && npx next start

open localhost:3000 and just refresh the root/home page a few times (the backend is not required for this page). Memory should shoot up to 400-500mb. In production this was consuming 2gb (all memory available)

Production version is - https://xmplaylist.com/ you can see the home page has a good set of images.

[frigus02]

We experience this as well. We use Next.js for a shop-like website, which has 60-100 images per page. After updating Next.js from 10.0.7 to 10.0.8 our memory usage jumped from ~600MB to ~3.7GB

With 10.0.7:

With 10.0.8:

We reverted to 10.0.7 and memory usage is back to ~600MB.

We can't say for sure if this is related to images. But we did see a general increase in response time for /_next/image URLs together with the memory increase while other routes didn't show an increased response time.

[jnv]

I can confirm the same issue. We run our app in container with limited memory and since update to 10.0.8 we started to get regular out-of-memory crashes even though there were just two images going through /_next/image endpoint – 256M were not sufficient. In our case it was easier to avoid use of next/image altogether.

[underfisk]

It's also happening to me, more than this issue but its one critical issue even on the optimization of the images, its suffering with response time

[r3na]

+1

[muntasirsyed]

10.0.8 was supposedly supposed to fix this issue by switching out the sharp library for a wasm equivalent but it's made it even worse. We've had to rollback all usage of next/image now in production unfortunately.

It was consuming literally all memory available on our ec2 instances.

[shuding]

We've identified the cause and are working on a fix, but it would be helpful if you can share more info for this! I.e. number of CPU cores, average image size, memory increased after upgrading, etc.

[karlhorky]

I know @Thoud was experiencing this the other day, deploying his Next.js bootcamp project to the Heroku free plan...

[chemicalkosek]

Having the same thing.
Next.js website deployed to dokku container.
2cpu Digital Ocean droplet.

There are only two Image component images (original image sizes approx 300kb and 20kb)
Each website reload (when the 60 seconds image cache ends) adds 100-200MB to memory usage.
I noticed by having alerts from netdata about low memory on server.
At that point the affected nextjs website had 2.4GB memory usage.

After reverting to 10.0.7 much better, but still more memory usage than much bigger next.js apps without Image component.
Still rises by about 20-25MB on each reload. I will see how it goes.
Edit: I think it has stabilized at around 260MB

[fostyfost]

Hi!
@Timer @timneutkens
Why does #23077 close this and #20915 issues? This may be a mistake. This issue is still relevant. You need to open this issue again.

[timneutkens]

@fostyfost it's fixed on the canary line. Please try installing next@canary.

[fostyfost]

@timneutkens please tell me which commit fixes this issue?

[timneutkens]

#23077

[Trallp]

@timneutkens Just built and started on my mac (not m1) the same project and opened the same page with ~10 next/image images

10.0.7 ~ 118 MB:

10.0.10-canary.2 ~ 826 MB:

Sorry for Activity Monitor but even here the problem is obvious

[jakubjo]

I can confirm this. I had the same memory issues when deployed to production. Even using next@canary.
Downgrade to next.js 10.0.7 has resolved the issues. Ubuntu 20.04.

[gu-stav]

@shuding Unfortunately you good work doesn't fix the issue for me (even on v10.0.10-canary.7). It still exceeds 1960MB, where as it uses much less memory in 10.0.7 (230MB).

[karlhorky]

I guess the new issue tracking this problem is over here: #23189

[balazsorban44]

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.