JVM Crash on V [libjvm.so+0xab4d83] PhaseCFG::call_catch_cleanup(Block*)+0xa3

Per Liden per.liden at oracle.com
Thu Dec 12 08:39:02 UTC 2019


Hi,

At one point there were a couple of issues related to catch cleanup. 
These were all fixed by 
https://bugs.openjdk.java.net/browse/JDK-8230565, which was backported 
to 13.0.2 and will be released next month.

In the mean time, a workaround could be to exclude the offending 
method(s) from being compiled by C2. Depending on what you're doing, 
another option might be to use the latest JDK 14-ea build.

cheers,
Per

On 12/12/19 2:44 AM, Sundara Mohan M wrote:
> Hi,
>    I was trying JVM 13.0.1+9 with ZGC and observing this crash
> 
> Host: Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz, 48 cores, 125G, Red Hat
> Enterprise Linux Server release 6.10 (Santiago)
> Time: Wed Dec 11 05:41:55 2019 UTC elapsed time: 34571 seconds (0d 9h 36m
> 11s)
> 
> ---------------  T H R E A D  ---------------
> 
> Current thread (0x00007f6ab016e5b0):  JavaThread "C2 CompilerThread0"
> daemon [_thread_in_native, id=48663,
> stack(0x00007f67b55a7000,0x00007f67b56a8000)]
> 
> 
> Current CompileTask:
> C2:34571629 42982   !   4
> net.htmlparser.jericho.Attributes::construct (1337 bytes)
> 
> Stack: [0x00007f67b55a7000,0x00007f67b56a8000],  sp=0x00007f67b56a3330,
>   free space=1008k
> Native frames: (J=compiled Java code, A=aot compiled Java code,
> j=interpreted, Vv=VM code, C=native code)
> V  [libjvm.so+0xab4d83]  PhaseCFG::call_catch_cleanup(Block*)+0xa3
> V  [libjvm.so+0x80aadf]  PhaseCFG::global_code_motion()+0x8bf
> V  [libjvm.so+0x80ae7a]  PhaseCFG::do_global_code_motion()+0x4a
> V  [libjvm.so+0x634c95]  Compile::Code_Gen()+0x1d5
> V  [libjvm.so+0x6386a0]  Compile::Compile(ciEnv*, C2Compiler*, ciMethod*,
> int, bool, bool, bool, DirectiveSet*)+0xdc0
> V  [libjvm.so+0x55fadc]  C2Compiler::compile_method(ciEnv*, ciMethod*, int,
> DirectiveSet*)+0xbc
> V  [libjvm.so+0x64229d]
>   CompileBroker::invoke_compiler_on_method(CompileTask*)+0x3fd
> V  [libjvm.so+0x643c70]  CompileBroker::compiler_thread_loop()+0x5d0
> V  [libjvm.so+0xf6b9fe]  JavaThread::thread_main_inner()+0x1be
> V  [libjvm.so+0xf707fd]  Thread::call_run()+0x10d
> V  [libjvm.so+0xc875b7]  thread_native_entry(Thread*)+0xe7
> 
> ...
> 
> Came across this bug https://bugs.openjdk.java.net/browse/JDK-8225509
> 
> 
> Seeing this frequently with 13.0.1+9 JVM. Assuming this is specific to ZGC
> 1. Can someone give more info when this can happen?
> 2. Since 13.0.2 is targeted for Jan 2020, is there a workaround to fix this
> in 13.0.1?
> 
> Thanks
> Sundar
> 


More information about the zgc-dev mailing list