-
Bug
-
Resolution: Fixed
-
P4
-
8u192, 9, 10, 11, 12, 13
-
b16
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8319088 | 11.0.23-oracle | Ivan Bereziuk | P4 | Resolved | Fixed | b01 |
This causes failures for tests that use the used() value of that MemoryMXBean (linked below) as they do not expect such large jumps in usage after allocation of a few (more) objects in survivor space.
This is day one behavior (and some of these tests have been excluded from testing for a long time now).
After fixing, also re-enable the corresponding tests, verifying that they work again.
- backported by
-
JDK-8319088 Survivor MemoryMXBean used() size granularity is region based
- Resolved
- blocks
-
JDK-8081688 SurvivorAlignmentInBytes tests too lenient
- Closed
-
JDK-8220089 G1 reuse survivor region as eden region at the end of gc
- Open
- duplicates
-
JDK-8177765 gc/survivorAlignment/TestPromotionFromSurvivorToTenuredAfterMinorGC.java: Actual memory usage should not deviate from expected
- Closed
-
JDK-8190277 TestPromotionToSurvivor - Actual memory usage should not deviate from expected
- Closed
-
JDK-8129886 Test TestPromotionToSurvivor fails with jimage refresh
- Closed
- is blocked by
-
JDK-8209062 Clean up G1MonitoringSupport
- Resolved
- relates to
-
JDK-8221994 Improve consistency between actual values and MemoryUsage.used() in MBeans
- Open