-
Notifications
You must be signed in to change notification settings - Fork 41
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
Too Many file open error #117
Comments
Hey guys , I can reproduce bug.. And
This |
Yeah .. I tried increasing Interestingly when i revert browserify/resolve@e83630d commit all things looks fine. Am I missing something here ? |
@chetandhembre: browserify/browserify#1003 also proposes increasing ulimit (to 2048), but if you're at 10480, then you'll need to go a lot higher. I'm not sure if that number of open files is excessive or expected. At first I assumed it was excessive, given your report about it being far higher on the latest version of node-resolve, but after reading the issue that the latest version fixes (browserify/resolve#76), I realized it would be expected to be a lower number on the older (buggy) version. Perhaps the best way to determine if it's a bug or not would be to examine the files that are open with and without the browserify/resolve@e83630d commit (maybe this article is helpful? I'm guessing you have OSX, maybe the "Unix" instructions will work?) Usually node packages will use https://github.com/isaacs/node-graceful-fs if they're running into EMFILE errors. It handles a number of things, but its primary purpose is "fs with incremental backoff on EMFILE". If the large number of files is expected, it could be that node-resolve needs to use node-graceful-fs to gracefully handle it. |
@prust thanks for such details response.. I will definitely use your suggestion. May be next weekend I will look into it again |
Hi guys ,
I am using code fetch from here and I just upgraded to my packages to later versions.
After starting server I am getting following error
Can any one help me here ?
The text was updated successfully, but these errors were encountered: