RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Reproducer at https://bugs.openjdk.java.net/browse/JDK-8132985
also crashes in Fedora 29. So, should affect all java-1.8.0-packages
in rhel and fedora.
Patch is also available at bugs.openjdk.java.net.

Also reported at
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210226

Assigning to Severin, since he is working already on the upstream backport

Backport fixes have been pushed upstream:

http://hg.openjdk.java.net/jdk8u/jdk8u-dev/jdk/rev/3d0c0934a949
http://hg.openjdk.java.net/jdk8u/jdk8u-dev/jdk/rev/b5fa49bf0430

This should get picked up with the OpenJDK April CPU release.

Hi! Can this update be with pre-cpu update or is it ciritcal enough to go with closest batch?

Clarified, will be included in next CPU, this acking, as there is reserved workload for this time.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2006