| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8205829 | 11.0.1 | Thomas Schatzl | P4 | Resolved | Fixed | team |
When deciding that a given humongous starts region remembered set should be dropped because we never reclaim it (because of large remembered set), the humongous continues region remembered sets are not updated.
There is no real issue with that as HC remembered sets are always empty, just annoying to look at in the logs, so I am filing this as an RFE.
Occurs eg. with gc/g1/TestEagerReclaimHumongousRegionsClearMarkBits.
There is no real issue with that as HC remembered sets are always empty, just annoying to look at in the logs, so I am filing this as an RFE.
Occurs eg. with gc/g1/TestEagerReclaimHumongousRegionsClearMarkBits.
- backported by
-
JDK-8205829 Humongous continues region remembered set states do not match the one from the corresponding humongous start region
-
- Resolved
-
- relates to
-
JDK-8205426 Humongous continues remembered set does not match humongous start region one after Remark
-
- Closed
-
-
-
- Closed
-