SIGSEGV with build 9.0.1+11

[David Holmes]

On 20/03/2018 8:20 AM, Vladimir Kozlov wrote:
> Hi Nezih,
> 
> Such failures happens due to bad oops (java object pointers) due to 
> different reasons. And it is very hard to reproduce or find the cause. I 
> can't guarantee that we will be able to fix this particular case (your 
> program ran for 8 days and had millions of JIT compilations).
> 
> I filed bug to record this failure:
> 
> https://bugs.openjdk.java.net/browse/JDK-8199804

But please note Nezih that the OpenJDK mailing lists are _not_ for 
reporting bugs.

# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp

Thanks,
David

> Regards,
> Vladimir
> 
> On 3/19/18 1:50 PM, nezih yigitbasi wrote:
>> In case the attachment doesn't make it, here is the hs_err file:
>> https://gist.github.com/nezihyigitbasi/427919d3c86b4d86281ee1f33f96a23e
>>
>> Thanks,
>> Nezih
>>
>> 2018-03-19 11:43 GMT-07:00 nezih yigitbasi <nezihyigitbasi at gmail.com>:
>>> Hi,
>>> Our production app recently crashed with a SIGSEGV at
>>> "~BufferBlob::vtable chunks" with Java build 9.0.1+11. This is the
>>> first time we see a crash with this particular stack after upgrading
>>> to Java 9. A quick search leads to JDK-8169938 (which is related to
>>> AOT compiled binaries and we don't use AOT) and JDK-8191081, which is
>>> closed as incomplete. You can find the hs_err file in the attachment.
>>>
>>> Any help is greatly appreciated.
>>>
>>> Thanks,
>>> Nezih