SIGSEGV crash in ObjectMonitor::enter with latest Shenandoah JDK8

[Alexander Yakushev]

Hello folks,

I am terribly sorry for putting this off for too long. A few days ago, I
finally tried reproducing the bug again, with JDK8 from 20200228, and it no
longer occurs. I've been running the system on regular load for two days
now – before, it usually crashed within a few hours.

So, whatever the issue was, it no longer happens, which is great! Thanks
for the help, and sorry for leaving you hanging.

Best regards,
Alexander

On Fri, 15 Nov 2019 at 12:50, Roman Kennke <rkennke at redhat.com> wrote:

> Hi Alexander,
>
> > Sorry, I didn't have a chance to continue the investigation. We've
> > reverted to Shenandoah 1.0 since then and researched what it takes to
> > move this particular service to JDK11 (which is a good idea anyway).
>
> Hmm, ok. I'd sleep better if I could fix this bug. Or at least,
> reproduce it. Or know if it's still present, even.
>
> > I've noticed on Twitter that you managed to trigger a similar problem
> > with Netty in the same method (ScheduleFutureTask.cancel). Did it lead
> > anywhere?
>
> No. This was an attempt to reproduce your problem. But I did not manage
> to reproduce it so far.
>
> I'll keep digging.
>
> Thanks,
> Roman
>
>