Troubles with Shenandoah

[Simone Bordet]

Hi,

On Sun, Apr 7, 2019 at 2:50 PM Aleksey Shipilev <shade at redhat.com> wrote:
>
> On 4/7/19 2:41 PM, Simone Bordet wrote:
> > I have 2 questions:
> >
> > A) is the version I'm using a "stable" enough version (it's this one:
> > https://builds.shipilev.net/openjdk-jdk12/openjdk-jdk12-latest-linux-x86_64-release.tar.xz)
>
> That is basically 12u bleeding edge for testing, and it might be broken. The releases that ship by
> major vendors are usually much more stable.

Found at AdoptOpenJDK the stable one, but the problem still occurs.
I have added -XX:+ShenandoahVerify, I see no crashes and typical output is:

[2019-04-07T09:13:01.120-0500][info][gc,start      ] GC(15) Verify
After Updating References, Level 4
[2019-04-07T09:13:01.257-0500][info][gc            ] GC(15) Verify
After Updating References, Level 4 (6178264 reachable, 192 marked)

Not sure if it's correct.

Trying now with -XX:ShenandoahGCHeuristics=passive.

-- 
Simone Bordet
---
Finally, no matter how good the architecture and design are,
to deliver bug-free software with optimal performance and reliability,
the implementation technique must be flawless.   Victoria Livschitz