Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionAndrew John Hughes
2020-04-22 18:30:44 UTC
This bug was initially created as a copy of Bug #1751985
I am copying this bug because:
Same change needed for java-11-openjdk.
Description of problem:
We observe the slowdown in our product (an xtext and Eclipse based DSL development environment). We have many loaded classes and believe we observe OpenJDK bug 8227269. So we believe this OpenJDK ticket is the actual cause:
https://bugs.openjdk.java.net/browse/JDK-8227269
Version-Release number of selected component (if applicable):
socbl958:/home/sandreev$ java -version
openjdk version "1.8.0_181"
OpenJDK Runtime Environment (build 1.8.0_181-b13)
OpenJDK 64-Bit Server VM (build 25.181-b13, mixed mode)
socbl958:/home/sandreev$ cat /etc/redhat-release
Red Hat Enterprise Linux Workstation release 7.4 (Maipo)
How to reproducible:
1. Execute the main method found in the attached "Looper.zip". Observe the total running time (on my HP Z620 its about 30 seconds).
2. Execute the same main method with a debug agent ("-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=8100" command line argument) and attach some debugger. E.g. I use the Eclipse one. Observe the total running time (on my HP Z620, about 50 seconds).
Actual results:
Execution time with an attached debugger, when loading classes, is much higher than without an attached debugger.
Expected results:
If the debugger installs no breakpoints and doesn't interfere with the execution, execution time should be at most marginally higher.
Execution in debug mode (with a debug agent attached) should not be taking much longer than normal execution, if the agent is not pausing the JVM or has installed breakpoints.
Additional info:
We would like a fix for
https://bugs.openjdk.java.net/browse/JDK-8227269 in Java 1.8 to avoid the problem described above.
Comment 1Andrew John Hughes
2020-05-23 11:01:38 UTC
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 (java-11-openjdk bug fix and enhancement update), 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-2020:3919