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.

Sign up for GitHub

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

Jump to bottom

vfork failing unless excessively large swap space configured #1286

Closed
chesterm8 opened this issue Oct 28, 2016 · 1 comment
Closed

vfork failing unless excessively large swap space configured #1286

chesterm8 opened this issue Oct 28, 2016 · 1 comment
Labels
bug duplicate

Comments

@chesterm8
Copy link

Simple java class to reproduce the issue: Gist

Compiled and run using

At 5000MB the following is seen:

[bellchesters@DESKTOP]$ java -version
java version "1.8.0_101"
Java(TM) SE Runtime Environment (build 1.8.0_101-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.101-b13, mixed mode)
[bellchesters@DESKTOP]$ javac Main.java
[bellchesters@DESKTOP]$ strace -ff java Main 2>&1 | grep vfork
[pid  2398] vfork()                     = -1 ENOMEM (Cannot allocate memory)

At 16000MB the operation completes successfully.
@chesterm8 chesterm8 mentioned this issue Oct 28, 2016
Closed
@pboos pboos mentioned this issue Nov 11, 2016
Closed
@therealkenc therealkenc mentioned this issue Nov 21, 2016
Closed
@benhillis
Copy link
Member

Marking this as a duplicate of #851 - see my comment about the incoming fix #851 (comment)

@seancorfield seancorfield mentioned this issue Jan 12, 2017
Closed
@therealkenc therealkenc mentioned this issue Feb 28, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug duplicate
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@chesterm8 @therealkenc @benhillis