-
Notifications
You must be signed in to change notification settings - Fork 302
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
EMFILE or ENOENT when building for osx #180
Comments
Which version of node-webkit-builder have you? |
I'm afraid I can't access the version number because of the line endings issue reported elsewhere. No matter which way I call the file from terminal, I get env: node\r: No such file or directory Sorry I can't be more useful! |
@jthrilly you can see in |
I have exactly same error, my version of |
I am also receiving the identical error message with version |
Same here for |
Experiencing the same issue as well. |
Could someone try again with 1.0.10? |
1.0.10 fixed this issue for me, I guess. My app now builds for OS X (OS X 10.10.2) without error, but it does not execute. On execution, console log shows:
May be unrelated, I'm still researching |
I can confirm that 1.0.10 solved this issue for me on Windows 👍 |
For me it works fine now on osx. Thanks. |
Closing. I'll reopen if this happens for anyone still. |
I just updated to 1.0.11 this morning, and I'm still seeing EMFILE errors during my build. I'm on Mac OS X Yosemite 10.10.2. |
There there... It will all be better someday :) Let me know if there's anything I can do to help. Do you need any logfiles or anything? |
@benjismith Is the error consistent (i.e happens every time)? |
Yes, it happens every time. |
Is is possible for you to paste your package.json here, specifically the dependencies? |
|
So the builder sits in the same directory as the application? (you have one or two package.json) |
It looks like this:
|
Was hoping you'll have two. In any case, can you try deleting all the non dev dependencies and run the build? |
I tried deleting the dependencies and building again, and it doesn't help. I also tried building on windows, and that doesn't help either. It seems like the root cause of the problem here is trying to simultaneously copy thousands of files using async operations. Is that really necessary? Is there any advantage? Why not just loop through the files and copy them synchronously, one at a time? |
Same EMFILE error on version 1.1.0, on Yosemite and Ubuntu 14.10. |
Same here OSX 10.10.2 and node-webkit-builder 1.0.11. Had the EMFILE error 20, then after updating node to 0.12.0 and npm to 2.7.0 I have the same error, but with error number -24 My app folder has 2063 files. Interesting, cause I have some npm scripts and gulp scripts that copy the whole folder and this never happens. |
@chino32 try the latest one On Thu, 12 Mar 2015 09:39 chino23 [email protected] wrote:
|
hmm @adam-lynch am I missing something? :) I'm already using the latest version of node-webkit-builder, and there hasn't been any changes in the last 24 hours as I can see. |
My mistake, @chino23. I was thinking the latest was |
Same here, Linux 3.18.6, node-webkit-builder 1.0.11. |
Could this be related to #204 ? |
I started getting ENFILE errors after adding a particularly large library to my project. I have traced down the issue and it appears to be caused by this code in NwBuilder.mergeAppFiles(): If I understand the code correctly, that line attempts to copy every file in the project simultaneously. You might get lucky enough for some of the files to finish before it starts more, but eventually, you will hit the limit of how many open files you can have. I made a fix locally, limiting the number of concurrent copies and no longer have the issue. @adam-lynch If you don't mind bluebird being updated to 2.x.x, I can submit a PR (I use the 2.0 |
I would love a fix for that! |
Similar error, sorry. Windows 64.
package.json
|
I @adam-lynch, ty. I try now with "nw": "0.12.2", but the result... Fatal error: ENOENT: no such file or directory, lstat 'c:\Users\marcos\documents\jsLabs\libr\cache\0.13.0-beta2\win32\ffmpegsumo.dll' |
@mmfilesi oh no, what I mean is when you're calling var NwBuilder = require('nw-builder');
var nw = new NwBuilder({
files: './path/to/nwfiles/**/**', // use the glob format
platforms: ['osx32', 'osx64', 'win32', 'win64'],
version: '0.12.2'
}); That should work fine. |
Thats work fine : ) : ) : ) Ty adam-lynch, !!!! |
I haven't heard about this problem in a long long time. I think it's ok. Fixes have also been released today by the way (newer NW.js versions are support, alpha/beta builds, etc.) |
For my app building for win32 and win64 works fine, but building for any osx platform will result in either an EMFILE or ENOENT error.
I'm running Yosemite 10.10.2, so having the usual trouble with ulimit not working. However, launchctl limit maxfiles reports:
maxfiles 10240 10240
and ulimit -n reports 1024.
Examples of errors:
The text was updated successfully, but these errors were encountered: