-
Notifications
You must be signed in to change notification settings - Fork 847
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
Error: EMFILE: too many open files #1126
Comments
Hi @jcimoch -- thanks for reporting this! In my experience, nodejs is very good at using up lots of file descriptors, which can lead to
That will print out the maximum number of files that an application launched in that shell is allowed to open. I'm wondering if someone or something might have raised those limits in your other environments. |
It is 256 on OSX. I don't have access to ubuntu right now but i assume same or bigger limit. |
@jcimoch It might be interesting to look at your process in /proc/[pid]/fd to see how many file descriptors are open and what they are. I suspect there might be some other call in your project that is failing and leaking file descriptors (maybe due to an earlier failure in WSL). For example:
|
It seems it is well known issue https://hexo.io/docs/troubleshooting.html#EMFILE-Error. I have also tested it with native windows node.js instalation and there is the same problem. So it is not connected to windows bash but more like system IO. |
Marking as a duplicate of #1688 which will be fixed in Insider builds soon. |
I was trying to start my project which was previously developed under OSX system. I cloned my git repository and tryied to run it under new windows subsytem for linux. Unfortunatelly it won't work out of the box.
Windows 10 Pro N 64-bit (10.0, Build 14393) (14393.rs1_release_inmarket.160906-1818)
My node.js version is 6.6.0
All the same commands and packages versions works fine under OSX or native Linux.
I think that might be related to windows bash implementation, because it works without problems on other UNIX like systems.
The text was updated successfully, but these errors were encountered: