Error: EMFILE: too many open files

[moaazbhnas228]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Pro
    Binaries:
      Node: 18.16.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant Packages:
      next: 13.4.10-canary.6
      eslint-config-next: 13.4.3
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 4.8.2
    Next.js Config:
      output: N/A

Which area(s) of Next.js are affected? (leave empty if unsure)

Middleware / Edge (API routes, runtime)

Link to the code that reproduces this issue or a replay of the bug

Unfortunately, it's a private repo, and I can't provide a replay as it's a server error, but will do my best to describe it.

To Reproduce

Honestly, I'm not sure how to reproduce it.

Describe the Bug

Error message: "EMFILE: too many open files"

When does it happen:
It happens when the browser sends a "HEAD" request to our product page, and results in 500 Server Error in the browser.

Possible Cause:
I think it happens because Headless UI imports all its files every time a single component is used.

How can I fix this? Is there a way to maximize the number of allowed open files in the server?

Expected Behavior

The server error not to happen

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

Vercel

[github-actions]

We cannot recreate the issue with the provided information. Please add a reproduction in order for us to be able to investigate.

Why was this issue marked with the please add a complete reproduction label?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We prefer a link to a public GitHub repository (template for pages, template for App Router), but you can also use these templates: CodeSandbox: pages or CodeSandbox: App Router.

To make sure the issue is resolved as quickly as possible, please make sure that the reproduction is as minimal as possible. This means that you should remove unnecessary code, files, and dependencies that do not contribute to the issue.

Please test your reproduction against the latest version of Next.js (next@canary) to make sure your issue has not already been fixed.

I added a link, why was it still marked?

Ensure the link is pointing to a codebase that is accessible (e.g. not a private repository). "example.com", "n/a", "will add later", etc. are not acceptable links -- we need to see a public codebase. See the above section for accepted links.

What happens if I don't provide a sufficient minimal reproduction?

Issues with the please add a complete reproduction label that receives no meaningful activity (e.g. new comments with a reproduction link) are automatically closed and locked after 30 days.

If your issue has not been resolved in that time and it has been closed/locked, please open a new issue with the required reproduction.

I did not open this issue, but it is relevant to me, what can I do to help?

Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps. Furthermore, you can upvote the issue using the 👍 reaction on the topmost comment (please do not comment "I have the same issue" without reproduction steps). Then, we can sort issues by votes to prioritize.

I think my reproduction is good enough, why aren't you looking into it quicker?

We look into every Next.js issue and constantly monitor open issues for new comments.

However, sometimes we might miss one or two due to the popularity/high traffic of the repository. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority.

Upvoting issues to show your interest will help us prioritize and address them as quickly as possible. That said, every issue is important to us, and if an issue gets closed by accident, we encourage you to open a new one linking to the old issue and we will look into it.

Useful Resources

• How to Contribute to Open Source (Next.js)
• How to create a Minimal, Complete, and Verifiable example
• Reporting a Next.js bug
• Next.js Triaging issues

[Tamicktom]

Sorry for English.

The same is happening in my project. It does the build and deploy process normally in vercel, but when I try to access the login page, the same error happens.

When I run it on my local machine, it works normally.

I'm using Prisma with next-auth.

My repository link: https://github.com/Tamicktom/hammertail

Feel free to use my project to recreate the error.

[Tamicktom]

Sorry for bad English

I solved the problem in my project. In my case the trigger was phosphor-icons/react.

Nextjs was having trouble importing the icons (not sure).

I solved it by adding a setting to next.config as shown in a comment of a phosphor-icons/react issue on the same subject: phosphor-icons/react#45 (comment)

Which is strange, as this problem is only happening when placing the project in vercel.

[moaazbhnas228]

Thank you @Tamicktom,
I think Vercel has a max number of modules, and it got exceeded because I was loading the whole lodash library files.
To fix this I used Next.js new feature Modularize Imports

[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.