JVM Crashes after few hours
Rajesh.Agarwal at snapon.com
Tue Nov 22 16:30:55 UTC 2016
The method on which the compiler breaks keep changing. But we are seeing that at mist of the instance the compiler breaks at find_method_index method of InstanceKlass.
Another thing is, we are facing this issue only when caching is enabled which is based on Google Guava and kryo. In prd env, the app is working fine with caching but the new version in load test env is failing.
On Tue, Nov 22, 2016 at 9:37 PM +0530, "kirk at kodewerk.com" <kirk at kodewerk.com<mailto:kirk at kodewerk.com>> wrote:
It looks as though the C2 compiler is failing to find this method when it is trying to inline it. com.snapon.sbs.cstone.domain.partsearch.sorting.PartSearchRankSortScorer::indexOfGroup. Can you decompile the class to make sure the method is there (more than likely it is there or HotSpot wouldn’t consider it for inlining). If so you can set a hot spot directive to not compile this method. And, you can file a bug (if one hasn’t already been filed).
> On Nov 22, 2016, at 5:39 PM, Agarwal, Rajesh <Rajesh.Agarwal at snapon.com> wrote:
> Attached is the complete log.
> Rajesh Agarwal
> -----Original Message-----
> From: kirk at kodewerk.com [mailto:kirk at kodewerk.com]
> Sent: Tuesday, November 22, 2016 8:55 PM
> To: Agarwal, Rajesh <Rajesh.Agarwal at snapon.com>
> Cc: hotspot-compiler-dev at openjdk.java.net
> Subject: Re: JVM Crashes after few hours
> Can we see the rest of the log? This view of the log has cut off important information.
> Kind regards,
> Kirk Pepperdine
>> On Nov 22, 2016, at 8:43 AM, Agarwal, Rajesh <Rajesh.Agarwal at snapon.com> wrote:
>> The JVM either crashes or hangs after running for few hours with following error.
>> # A fatal error has been detected by the Java Runtime Environment:
>> # SIGSEGV (0xb) at pc=0x00007f93aa58ed32, pid=24048,
>> tid=0x00007f9368a68700 # # JRE version: Java(TM) SE Runtime
>> Environment (8.0_112-b15) (build 1.8.0_112-b15) # Java VM: Java
>> HotSpot(TM) 64-Bit Server VM (25.112-b15 mixed mode linux-amd64
>> compressed oops) # Problematic frame:
>> # V [libjvm.so+0x640d32]
>> InstanceKlass::find_method_index(Array<Method*>*, Symbol*, Symbol*,
>> bool, bool)+0x42 # # Failed to write core dump. Core dumps have been
>> disabled. To enable core dumping, try "ulimit -c unlimited" before
>> starting Java again # # If you would like to submit a bug report, please visit:
>> # http://bugreport.java.com/bugreport/crash.jsp
>> --------------- T H R E A D ---------------
>> Current thread (0x00007f93a4a50800): JavaThread "C2 CompilerThread0"
>> daemon [_thread_in_vm, id=24067,
>> siginfo: si_signo: 11 (SIGSEGV), si_code: 2 (SEGV_ACCERR), si_addr:
>> vm_info: Java HotSpot(TM) 64-Bit Server VM (25.112-b15) for
>> linux-amd64 JRE (1.8.0_112-b15), built on Sep 22 2016 21:10:53 by
>> "java_re" with gcc 4.3.0 20080428 (Red Hat 4.3.0-8)
>> VM Arguments:
>> jvm_args: -Xms2560m -Xmx2560m -XX:-UseAdaptiveSizePolicy
>> -XX:NewRatio=2 -XX:SurvivorRatio=2 -XX:TargetSurvivorRatio=80
>> -Xnoclassgc -verbose:gc -XX:+PrintGCDateStamps
>> -XX:+HeapDumpOnOutOfMemoryError -XX:-ReduceInitialCardMarks
>> -XX:+UseG1GC -XX:MaxGCPauseMillis=400 -XX:CICompilerCount=2
>> -XX:+UnlockDiagnosticVMOptions -XX:+LogCompilation Thanks Rajesh
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the hotspot-compiler-dev