best jvm crash ever. On Mon, Feb 8, 2016 at 9:54 PM, Policeman Jenkins Server <[email protected]> wrote: > [junit4] >>> JVM J2 emitted unexpected output (verbatim) ---- > [junit4] # > [junit4] # A fatal error has been detected by the Java Runtime Environment: > [junit4] # > [junit4] # SIGSEGV (0xb) at pc=0x89c03155, pid=14255, tid=14333 > [junit4] # > [junit4] # JRE version: ˆ„K÷ +¡àø+¡à (9.0+104) (build ) > [junit4] # Java VM: Java HotSpot(TM) Server VM > (9-ea+104-2016-02-03-214936.javare.4385.nc, mixed mode, tiered, concurrent > mark sweep gc, linux-x86) > [junit4] # Problematic frame: > [junit4] # C 0x89c03155 > [junit4] # > [junit4] # No core dump will be written. Core dumps have been disabled. To > enable core dumping, try "ulimit -c unlimited" before starting Java again > [junit4] # > [junit4] # An error report file with more information is saved as: > [junit4] # > /home/jenkins/workspace/Lucene-Solr-trunk-Linux/lucene/build/codecs/test/J2/hs_err_pid14255.log > [junit4] [thread 15849 also had an error] > [junit4] [thread 14331 also had an error] > [junit4] [thread 14332 also had an error] > [junit4] > [junit4] [error occurred during error reporting , id 0xb] > [junit4] > [junit4] # > [junit4] # If you would like to submit a bug report, please visit: > [junit4] # http://bugreport.java.com/bugreport/crash.jsp > [junit4] # > [junit4] <<< JVM J2: EOF ---- >
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
