Strange bug inside jetty at shenandoah/jdk8u

[Aleksey Shipilev]

On 12/20/2017 12:12 AM, Kirill A. Korinsky wrote:
> Well,
> 
> Simpler case includes decreasing heap to 1Gb.
> 
> I attached two file:
>  - errors.log with jetty errors
>  - gc.log with gc.log
> 
> It run at fedora 27 openjdk-1.8.0 without fast debug.
> 
> Same setting but without Shenandoah doest reproduce this.
> 
> If I increase heap size this issue is making rare. Since 6Gb heap I can't reproduce it. Maybe it help.

GC logs and application logs are useless to debug the failure like this.

We need the actual VM error or other kind of hs_err-generating smoking gun. Or, at least the MCVE
that fails and debuggable, so we can take a look deeper here. I assume something like stripped down
embedded Jetty with trivial response handler fails? Tried to do this [1], and Shenandoah/8u runs
fine -- what is missing there? Since you seem to have the application that fails reliably, could you
strip it down to bare essentials that still fails?

Thanks,
-Aleksey

[1] https://github.com/shipilev/jetty-test