glibc 2.34 problems with Java SE 8

Florian Weimer fweimer@redhat.com
Sat Aug 7 11:29:50 GMT 2021


* Michael Brunnbauer:

> after upgrading to glibc 2.34, I have trouble with Oracle Java:
>
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0x00007ffb8ee408bc, pid=5589, tid=0x00007ffb8e4cc640
> #
> # JRE version: Java(TM) SE Runtime Environment (8.0_301-b09) (build 1.8.0_301-b09)
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.301-b09 mixed mode linux-amd64 compressed oops)
> # Problematic frame:
> # V  [libjvm.so+0x89a8bc]  method_comparator(Method*, Method*)+0x1c
>
> Another 4 systems where Java is not used (but MySQL, Python and other stuff)
> seem to be fine. Any idea?

We have been building and testing our OpenJDK 8 builds on glibc 2.34 for
a while.  I haven't heard about such problems.  I've asked internally
just to be sure.

If it doesn't reproduce with OpenJDK, you will likely have to talk to
Oracle.

Thanks,
Florian



More information about the Libc-help mailing list