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.
Bug 2196318 - SIGSEGV (duplicated predicate failed) in java.util.GregorianCalendar.computeTime() [rhel-8, openjdk-11]
Summary: SIGSEGV (duplicated predicate failed) in java.util.GregorianCalendar.computeT...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: java-11-openjdk
Version: 8.7
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Frederic Thevenet
QA Contact: OpenJDK QA
URL:
Whiteboard:
Depends On:
Blocks: 2222493 2222494 2222495 2222496 2222497
TreeView+ depends on / blocked
 
Reported: 2023-05-08 18:40 UTC by Peter Kurz
Modified: 2023-10-15 20:00 UTC (History)
11 users (show)

Fixed In Version: java-11-openjdk-11.0.20.0.8-2.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2222493 2222494 2222495 2222496 2222497 (view as bug list)
Environment:
Last Closed: 2023-09-08 08:07:15 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
hs_err (138.42 KB, text/plain)
2023-05-08 18:40 UTC, Peter Kurz
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-156669 0 None None None 2023-05-08 18:41:52 UTC
openjdk bug system JDK-8307683 0 None None None 2023-05-25 09:46:42 UTC
openjdk bug system JDK-8308884 0 None None None 2023-05-25 17:13:51 UTC

Description Peter Kurz 2023-05-08 18:40:15 UTC
Created attachment 1963296 [details]
hs_err

Description of problem:
Sporadically, calling java.util.GregorianCalendar.computeTime() leads to a crash. Disassembly of the compiled method is included in the attached hs_err file.

Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux release 8.7 (Ootpa)
openjdk version "11.0.19" 2023-04-18 LTS
OpenJDK Runtime Environment (Red_Hat-11.0.19.0.7-1.el8_7) (build 11.0.19+7-LTS)
OpenJDK 64-Bit Server VM (Red_Hat-11.0.19.0.7-1.el8_7) (build 11.0.19+7-LTS, mixed mode, sharing)

How reproducible:
It happens sporadically in a proprietary application. We were not able to reproduce the problem in an isolated environment.

Steps to Reproduce:
n/a

Actual results:
duplicated predicate failed which is impossible
SIGSEGV


Expected results:
No crash.


Additional info:
n/a

Comment 1 Peter Kurz 2023-05-08 18:45:12 UTC
Coredump is available on request (not posted as it contains sensitive data).

Comment 4 Severin Gehwolf 2023-05-25 09:46:43 UTC
Could you please try with this JVM option (disabling c2 compile of computeTime) and tell us if that works for you, please?

-XX:CompileCommand=exclude,java.util.GregorianCalendar::computeTime


Note You need to log in before you can comment on or make changes to this bug.