Memory Leak with Image Optimization in Next.js Docker Environment

[adgsenpai]

Link to the code that reproduces this issue

https://github.com/adgsenpai/imageleakdemo

To Reproduce

1. Create a Dockerfile for the Next.js application:

FROM node:21.1.0-alpine

WORKDIR /app

COPY package*.json ./
RUN npm install

COPY . .

RUN npm run build

EXPOSE 3000

CMD ["npm", "start"]

2. Build the image

docker build -t nextjs-app .

3. Run the docker container

docker run -p 3000:3000 nextjs-app

4. Access the application and observe the memory usage.

5. Enable image optimization by adding or ensuring the following in next.config.js:

module.exports = {
  images: {
    domains: ['your-domain.com'],
  },
};

6. Monitor the memory usage using Docker stats or any monitoring tool:

docker stats

Current vs. Expected behavior

Expected Behavior:
The Next.js application should run without any significant memory leaks, maintaining stable memory usage during operation.

Actual Behavior:
The application shows progressively increasing memory usage over time, leading to high memory consumption and potential crashes.

Provide environment information

Operating System:
      Platform: linux
      Arch: x64
      Version: Alpine Linux
    Binaries:
      Node: 20.11.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 12.1.6
      react: 17.0.2
      react-dom: 17.0.2

Which area(s) are affected? (Select all that apply)

Image (next/image)

Which stage(s) are affected? (Select all that apply)

next build (local)

Additional context

Deployment Platform: Docker
Reproducibility: The issue is consistently reproducible in the Docker environment. It does not occur when running the application locally outside of Docker.
Browsers: The memory leak is observed regardless of the browser used to access the application, indicating it is not browser-specific.
Environment: The issue has been specifically noted when running on Alpine Linux with the following setup:
Platform: linux
Arch: x64
Version: Alpine Linux

[jonsoku-dev]

nextjs is a really great framework but it's really tricky to use if it's not vercel..

[karlmacklin]

@vitalyiegorov Are you also on Docker on Alpine Linux?

We are seeing memory leaks on version 14.2.18 on alpine linux, in Docker, on Auzre, so it seems this is a perfect explanation for our problems.

Edit:

Celebrated too early..
@adgsenpai I cannot see what this issue states in your reproduction scenario.
I see memory go up for a bit initially, but it never starts accumulating, so it looks health.

[adgsenpai]

Thank you for your feedback. I was able to resolve the issue by updating the operating system and the version of Next.

[karlmacklin]

Thank you for your feedback. I was able to resolve the issue by updating the operating system and the version of Next.

You should probably close this issue then.

May I ask what operating system you updated to that fixed the issue for you?

[adgsenpai]

@karlmacklin Ubuntu 20.04

[github-actions]

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.