Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8082609 | emb-9 | Thomas Schatzl | P5 | Resolved | Fixed | team |
JDK-8086491 | 8u65 | Thomas Schatzl | P5 | Resolved | Fixed | b01 |
JDK-8078251 | 8u60 | Thomas Schatzl | P5 | Resolved | Fixed | b14 |
JDK-8137538 | emb-8u65 | Unassigned | P5 | Resolved | Fixed | b01 |
JDK-8079939 | emb-8u60 | Thomas Schatzl | P5 | Resolved | Fixed | team |
This makes that test fail, failing jprt.
Cause for this problem has been some wrong refactoring.
- backported by
-
JDK-8078251 TracePageSizes output reports wrong page size on Windows with G1
- Resolved
-
JDK-8079939 TracePageSizes output reports wrong page size on Windows with G1
- Resolved
-
JDK-8082609 TracePageSizes output reports wrong page size on Windows with G1
- Resolved
-
JDK-8086491 TracePageSizes output reports wrong page size on Windows with G1
- Resolved
-
JDK-8137538 TracePageSizes output reports wrong page size on Windows with G1
- Resolved
- relates to
-
JDK-8079208 gc/g1/TestLargePageUseForAuxMemory.java fails due to not considering page allocation granularity for setup
- Resolved
-
JDK-8058354 SPECjvm2008-Derby -2.7% performance regression on Solaris-X64 starting with 9-b29
- Resolved