Question regarding "native-compiled frame"

[Felix Yang]

Yes, the AArch64 port is doing the same thing as the x86 port.

I noticed this issue when I was trying to analyze a recent JVM crash issue
which triggers on the x86-64 platform with an official Oracle jdk8u121
release.

It turns out that this bug happens very rarely (triggered only once for my
Java workload and I am unable to reproduce it).

And I think it is the same as:
https://bugs.openjdk.java.net/browse/JDK-8146224 which is still pending
there.

Looking at the assembly instructions in the hs error log file, I find the
SIGSEGV is triggered by the last return statement of frame::sender
function.

Currently, I disabled the FindDeadLocks VM_Operation in my Java application
trying to lower the possibility of hitting the bug. But I am afraid that it
is something of a ticking bomb for us.

Thanks for your help,
Felix


On 18 September 2017 at 16:24, Andrew Haley <aph at redhat.com> wrote:

> On 16/09/17 10:43, Felix Yang wrote:
> > Thanks for this helpful information.
> > I performed JTreg and specjbb test and I find this code never hit on x86
> > platform.
> > So I also think of this return statement for x86 as dead code. Don't know
> > why the code is there.
>
> We'll probably never know.  We should take the x86 patch and apply it to
> AArch64
> for JDK 10.
>
> --
> Andrew Haley
> Java Platform Lead Engineer
> Red Hat UK Ltd. <https://www.redhat.com>
> EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671
>