-
Bug
-
Resolution: Fixed
-
P4
-
8u40
-
b120
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8163635 | 8u121 | Unassigned | P4 | Resolved | Fixed | b01 |
JDK-8156728 | 8u112 | Cheleswer Sahu | P4 | Resolved | Fixed | b01 |
JDK-8167742 | emb-8u121 | Unassigned | P4 | Resolved | Fixed | b01 |
"Max = 0K" in the following "Current rem set statistics" is confusing.
Total heap region code root sets sizes = 98K. Max = 0K.
0K ( 0.7%) by 93 Young regions
0K ( 0.0%) by 4 Humonguous regions
0K ( 0.6%) by 79 Free regions
96K ( 98.6%) by 336 Old regions
79865 code roots represented.
0 ( 0.0%) elements by 93 Young regions
0 ( 0.0%) elements by 4 Humonguous regions
0 ( 0.0%) elements by 79 Free regions
79865 (100.0%) elements by 336 Old regions
Region with largest amount of code roots =
511:(E)[0x00000000ffc00000,0x0000000100000000,0x0000000100000000], size = 0K,
num_elems = 0.
The size (i.e., in "Max" and "size") reported seems to be limited to
"strongly" reachable.
If the the max of code root sets size is 0K. The total should be 0K too.
Hence the confusing part.
The following flags have been used for the summary report:
-XX:+UnlockDiagnosticVMOptions -XX:+G1SummarizeRSetStats
-XX:G1SummarizeRSetStatsPeriod=10
- backported by
-
JDK-8156728 Confusing message in "Current rem set statistics"
-
- Resolved
-
-
JDK-8163635 Confusing message in "Current rem set statistics"
-
- Resolved
-
-
JDK-8167742 Confusing message in "Current rem set statistics"
-
- Resolved
-