Details
-
Bug
-
Resolution: Fixed
-
P2
-
hs25
-
b49
-
Not verified
Backports
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8024573 | 8 | Vladimir Kozlov | P2 | Closed | Fixed | b107 |
JDK-8034490 | 7u65 | Vladimir Kozlov | P2 | Resolved | Fixed | b01 |
JDK-8025420 | 7u60 | Vladimir Kozlov | P2 | Closed | Fixed | b01 |
Description
On the hotspot-dev mailing list on OpenJDK it was reported by Punya Biswal that a small Java program can trigger a crash with hotspot.
It seems like this is a C2 optimization that goes wrong. For some reason it only seem to happen with G1, so maybe it is related to some thing special that G1 does (the extra write barries?) but it is not a GC bug since the program does not trigger any GCs at all.
The issue is reported on 7u25, but it exists in the latest JDK8 build too (b103).
It is likely a C2 issue since running with -Xint or tiered compilation enabled does not cause the crash. Note that since tiered compilation is default in the later JDK8 builds it needs to be explicitly turned off for the reproducer to crash.
Making this a P2. Motivation:
Impact: High - crash
Likelihood: Low - Unsure about this. It seems to be a special case. But with the reproducer it happens every time.
Workaround: High. Don't know yet if particular tuning can be done. Currently the only workaround is to run with C1.
ILW=HLH -> P2
It seems like this is a C2 optimization that goes wrong. For some reason it only seem to happen with G1, so maybe it is related to some thing special that G1 does (the extra write barries?) but it is not a GC bug since the program does not trigger any GCs at all.
The issue is reported on 7u25, but it exists in the latest JDK8 build too (b103).
It is likely a C2 issue since running with -Xint or tiered compilation enabled does not cause the crash. Note that since tiered compilation is default in the later JDK8 builds it needs to be explicitly turned off for the reproducer to crash.
Making this a P2. Motivation:
Impact: High - crash
Likelihood: Low - Unsure about this. It seems to be a special case. But with the reproducer it happens every time.
Workaround: High. Don't know yet if particular tuning can be done. Currently the only workaround is to run with C1.
ILW=HLH -> P2
Attachments
Issue Links
- backported by
-
JDK-8034490 C2 optimization breaks with G1
- Resolved
-
JDK-8024573 C2 optimization breaks with G1
- Closed
-
JDK-8025420 C2 optimization breaks with G1
- Closed