You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by Kirk Lund <kl...@apache.org> on 2021/03/25 20:42:14 UTC
Precheckin job failed to fork JVM during compile
https://concourse.apachegeode-ci.info/builds/17742 core dumped during
compilation of one of the modules.
I believe exit code 134 means that it failed to fork a new Java VM.
I wonder what would cause a test job to be unable to fork a process. It
seems to have forked processes for compiling all of the other modules, so
it's not a persistent problem.
> Task :geode-membership:compileJava
#
# A fatal error has been detected by the Java Runtime Environment:
#
# Internal Error (methodData.cpp:1252), pid=8491, tid=0x00007f1716a78700
# fatal error: unexpected tag 32
#
# JRE version: OpenJDK Runtime Environment (8.0_282-b08) (build
1.8.0_282-b08)
# Java VM: OpenJDK 64-Bit Server VM (25.282-b08 mixed mode linux-amd64
compressed oops)
# Failed to write core dump. Core dumps have been disabled. To enable core
dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/geode/geode/geode-membership/hs_err_pid8491.log
<<<snip>>>
> Task :geode-membership:compileJava
#
# Compiler replay data is saved as:
# /home/geode/geode/geode-membership/replay_pid8491.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
<<<snip>>>
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':geode-membership:compileJava'.
> Compilation failed with exit code 134; see the compiler error output for
details.
Re: Precheckin job failed to fork JVM during compile
Posted by Donal Evans <do...@vmware.com>.
Hi Kirk,
This has been happening intermittently with the latest Liberica JDK8u282 since it was released. I worked with the folks at LIberica to reproduce the issue and they have a fix which will be included in their next release, sometime in April.
Donal
________________________________
From: Kirk Lund <kl...@apache.org>
Sent: Thursday, March 25, 2021 1:42 PM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: Precheckin job failed to fork JVM during compile
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fconcourse.apachegeode-ci.info%2Fbuilds%2F17742&data=04%7C01%7Cdoevans%40vmware.com%7C20e8e017a3554007e10608d8efce81a1%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637523017517864370%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=nxaQczcFxF8x%2FyYfy%2FU8OfL7CL2lLNoDpuIjJebJsIg%3D&reserved=0 core dumped during
compilation of one of the modules.
I believe exit code 134 means that it failed to fork a new Java VM.
I wonder what would cause a test job to be unable to fork a process. It
seems to have forked processes for compiling all of the other modules, so
it's not a persistent problem.
> Task :geode-membership:compileJava
#
# A fatal error has been detected by the Java Runtime Environment:
#
# Internal Error (methodData.cpp:1252), pid=8491, tid=0x00007f1716a78700
# fatal error: unexpected tag 32
#
# JRE version: OpenJDK Runtime Environment (8.0_282-b08) (build
1.8.0_282-b08)
# Java VM: OpenJDK 64-Bit Server VM (25.282-b08 mixed mode linux-amd64
compressed oops)
# Failed to write core dump. Core dumps have been disabled. To enable core
dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/geode/geode/geode-membership/hs_err_pid8491.log
<<<snip>>>
> Task :geode-membership:compileJava
#
# Compiler replay data is saved as:
# /home/geode/geode/geode-membership/replay_pid8491.log
#
# If you would like to submit a bug report, please visit:
# https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fbugreport.java.com%2Fbugreport%2Fcrash.jsp&data=04%7C01%7Cdoevans%40vmware.com%7C20e8e017a3554007e10608d8efce81a1%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637523017517864370%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=VLG8CUFcDaO8OpeMtX%2FBPoCNwt1dPOQrOJ%2BC4dTw%2FXE%3D&reserved=0
<<<snip>>>
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':geode-membership:compileJava'.
> Compilation failed with exit code 134; see the compiler error output for
details.