JVM crash with OS X

[hermeni...@gmail.com]

Hi

I am running a maven project and mvn test fail when it runs in a given sub-module.
It only fails on my OSX laptop, not on our Travis environment.
(The output at the end of the message)

If I run mvn test without jacoco. Everything is ok.
Anyone has a hint ?

My pom.xml: https://github.com/btrplace/scheduler/blob/master/pom.xml

My setup:
```
mvn --version
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
Maven home: /Users/fhermeni/Library/apache-maven-3.3.9
Java version: 1.8.0_66, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_66.jdk/Contents/Home/jre
Default locale: fr_FR, platform encoding: UTF-8
OS name: "mac os x", version: "10.11.1", arch: "x86_64", family: "mac"
```

The error message:
```
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00000001065cdeb8, pid=6779, tid=17411
#
# JRE version: Java(TM) SE Runtime Environment (8.0_66-b17) (build 1.8.0_66-b17)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.66-b17 mixed mode bsd-amd64 compressed oops)
# Problematic frame:
# V [libjvm.dylib+0x3cdeb8] PhaseIdealLoop::idom_no_update(Node*) const+0x12
#
# 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:
# /Users/fhermeni/Documents/Research/Projects/BtrPlace/Code/scheduler/choco/hs_err_pid6779.log
[thread 5891 also had an error]
#
# Compiler replay data is saved as:
# /Users/fhermeni/Documents/Research/Projects/BtrPlace/Code/scheduler/choco/replay_pid6779.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
#
/bin/sh: line 1: 6779 Abort trap: 6 /Library/Java/JavaVirtualMachines/jdk1.8.0_66.jdk/Contents/Home/jre/bin/java -javaagent:/Users/fhermeni/.m2/repository/org/jacoco/org.jacoco.agent/0.7.6.201602180812/org.jacoco.agent-0.7.6.201602180812-runtime.jar=destfile=/Users/fhermeni/Documents/Research/Projects/BtrPlace/Code/scheduler/choco/target/jacoco.exec -jar /Users/fhermeni/Documents/Research/Projects/BtrPlace/Code/scheduler/choco/target/surefire/surefirebooter8629494164943700960.jar /Users/fhermeni/Documents/Research/Projects/BtrPlace/Code/scheduler/choco/target/surefire/surefire3610797674310177082tmp /Users/fhermeni/Documents/Research/Projects/BtrPlace/Code/scheduler/choco/target/surefire/surefire_26882745415820677976tmp
```

[Marc R. Hoffmann]

Hi,

not sure whether we can do much about this. But can you please provide
the file

hs_err_pid6779.log

mentioned in the error message?

Regards,
-marc

--
Marc Hoffmann
hoff...@mountainminds.com
_______________________________________________
Mountainminds GmbH & Co. KG

Nussbaumstr. 4 * 80336 Muenchen * Germany
Phone/Fax +49-700-68664637 * 0700-MTNMINDS

Registergericht Muenchen * HRA 80201
Mountainminds Verwaltungs GmbH
Registergericht Muenchen * HRB 143183
Geschaeftsfuehrer Marc Hoffmann

[hermeni...@gmail.com]

Hi

I updated my JDK version just in case but no change.
Below is the last error message (to fit the attached log):

The log pastebin: http://pastebin.com/h8aYsw44

---

#
# A fatal error has been detected by the Java Runtime Environment:
#

# SIGSEGV (0xb) at pc=0x000000011054ba80, pid=10752, tid=0x0000000000004303
#
# JRE version: Java(TM) SE Runtime Environment (8.0_92-b14) (build 1.8.0_92-b14)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.92-b14 mixed mode bsd-amd64 compressed oops)
# Problematic frame:
# V [libjvm.dylib+0x3d0a80] PhaseIdealLoop::idom_no_update(Node*) const+0x12

#
# 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:

# /Users/fhermeni/Documents/Research/Projects/BtrPlace/Code/scheduler/choco/hs_err_pid10752.log

#
# Compiler replay data is saved as:

# /Users/fhermeni/Documents/Research/Projects/BtrPlace/Code/scheduler/choco/replay_pid10752.log
---

[Marc R. Hoffmann]

Hi,

ok, this is a known JDK bug we have already reported to OpenJDK:

https://bugs.openjdk.java.net/browse/JDK-8134862

Unfortunately not much we can do from our side.

Regards,
-marc