Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build throwing "EMFILE: too many open files" error #1980

Closed
furyd opened this issue Sep 23, 2021 · 3 comments
Closed

Build throwing "EMFILE: too many open files" error #1980

furyd opened this issue Sep 23, 2021 · 3 comments

Comments

@furyd
Copy link

furyd commented Sep 23, 2021

Describe the bug
When generating a large number of page, process fails with EMFILE: too many open files

To Reproduce
Generate a large number (I'm generating several hundred thousand pages) of records via a script in _data and run eleventy

Expected behavior
All pages generated without any error other than any user-code based bugs

Environment:

  • OS and Version: Windows 10 (on Parallels under Catalina 10.15.6)
  • Eleventy Version: 0.12.1
@zachleat zachleat assigned zachleat and unassigned zachleat Dec 18, 2021
@zachleat
Copy link
Member

Just ran into this on 1.x but I’m surprised to see it on 0.x?

0.x uses fs-extra which makes use of graceful-fs to solve this exact problem.

https://www.npmjs.com/package/graceful-fs

Can you double check the version you’re using?

Also can you report the exact erroring file name? Was it in the input directory (a read) or the output directory (a write)?

@zachleat
Copy link
Member

This was fixed for me on 1.x with #2139

@zachleat zachleat added this to the Eleventy 1.0.0 milestone Jan 9, 2022
@zachleat
Copy link
Member

zachleat commented Jan 9, 2022

This is an automated message to let you know that a helpful response was posted to your issue and for the health of the repository issue tracker the issue will be closed. This is to help alleviate issues hanging open waiting for a response from the original poster.

If the response works to solve your problem—great! But if you’re still having problems, do not let the issue’s closing deter you if you have additional questions! Post another comment and we will reopen the issue. Thanks!

@zachleat zachleat closed this as completed Jan 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants