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

1.0+beta18 "Too many open files" error #581

Closed
jfeser opened this issue Mar 4, 2018 · 4 comments
Closed

1.0+beta18 "Too many open files" error #581

jfeser opened this issue Mar 4, 2018 · 4 comments

Comments

@jfeser
Copy link
Contributor

jfeser commented Mar 4, 2018

Building core_kernel with jbuilder 1.0+beta18 fails on macos with the following error:

Error: exception Sys_error("/var/folders/_t/3zbr3_hx0sn0tlz6j7rdwdf00000gn/T/jbuilder9d9539.output: Too many open files")

Increasing the file descriptor count to 1024 solves the problem. It seems that jbuilder opens more files now, so the default of 256 is too low.

core_kernel-9805-e7966f.out.txt

@dra27
Copy link
Member

dra27 commented Mar 4, 2018

Can you test with #578 (opam pin add jbuilder https://github.com/dra27/jbuilder.git#limit-fds)?

@ghost
Copy link

ghost commented Mar 5, 2018

@dra27 I'm not sure this will make a big difference. get_std_output sets tail to false, we could try to fill this field properly. Setting to true will cause the process module to close the descriptor as soon as the command has been started.

Another thing I've been thinking about is that currently we might create too much interleaving in the scheduler. This shouldn't be too hard to fix, basically when a command finishes, we need to invoke the continuation before checking computations waiting for a free job slot.

@ghost
Copy link

ghost commented Mar 5, 2018

@dra27 actually I missed the Process.File ..., you fix seems good indeed

@jfeser
Copy link
Contributor Author

jfeser commented Mar 5, 2018

#578 fixes the problem on my side.

@ghost ghost closed this as completed Mar 14, 2018
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants