-
Notifications
You must be signed in to change notification settings - Fork 141
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
"Fatal error: EMFILE, open" when building osx distribution #103
Comments
You can try adding the following line to your
|
@adam-lynch that appears to have fixed it, many thanks! |
@kiyanwang no prob |
I have the same problem if I build a osx app on Windows 7! what can I do ? ulimit under Windows ? |
@smiling-Jack, sure it's the same problem? Maybe it's that you're ending up with paths which are too long for Windows? |
Yes i think so. My project has ca. 1280 files than i have remove many readme, test and liecens files and now i have 1113 files and no problems. But that's not a solution for the future. I now its strange ! |
Hmm @smiling-Jack, I've never heard of that before on Windows. |
If I set the option: |
I have found a solution ! :-) I have change in the "NwBuilder.prototype.mergeAppFiles" the return to: var x = Promise.all(copiedFiles) and it works for me. |
@smiling-Jack Have you made a pull request for this change? I am also having this issue on Windows 8. |
Is it possible to add the ulimit as an option in the Gruntfile? Just a thought that might make it easier on folks. Hope this helps! |
@jamesmortensen should that not be its own separate Grunt plugin? I'm more used to Gulp where making another simple plugin with a single purpose would be encouraged. |
I guess it could be its own plugin, but it's so simple that if you know you need to type "ulimit" it's just easier to type it out by hand than to look for a plugin. The only problem my suggestion would solve is to help those who don't know what ulimit is, which -- as Node.js grows and hits its "eternal September" -- would be something that could matter in the future. It's really not that big of a deal to type it at the terminal if it would go against the "keep it simple" and "single purpose" methodology to add it to grunt-node-webkit-builder. In other words, I think we all can live without it, at least those of us involved in the Node.js community today. Hope this helps clarify. |
It might not be a bad idea to add that to the documentation; however... Hope this helps! |
Added to READMEs. FYI, it should be fixed in Node 0.12 nodejs/node-v0.x-archive@6820054 |
I'm getting this error on OSX, even after trying:
or even
What else can I try? @adam-lynch |
I played around with a solution to problems like these... not sure if it solves it completely though. If you want to try, it's on the graceful-ncp branch of node-webkit-builder. So |
For others on mac who are still hitting this error on the latest version 1.0.0; try setting "macZip: true". For me this seemed to solve the issue. |
Thanks @mudcube, setting macZip to true solves the issue. So there are two different issue: one that can be solved using |
I'm using grunt-node-webkit-builder my config looks like this :
This worked fine whilst my _public folder (the node-webkit app ive written) did not contain a node_modules folder. However as soon as I include a node_modules folder I get this error:
It only errors for the OSX distribution, the others work fine.
I'm on Mavericks, running grunt-node-webkit-builder 0.2.1 which is using node-webkit-builder 0.1.1.
Also If I dont include the node_modules folder in the _public directory, then use the the grunt task to build the distribution it works, if I then manually copy the node_modules folder into
/Contents/Resources/app.nw/
in the dist folder, and run the app the app works perfectly. So I have a work around.Any thoughts on how I can prevent that error?
The text was updated successfully, but these errors were encountered: