-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P4
-
Affects Version/s: hs25
-
Component/s: hotspot
-
b11
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8004520 | 8 | Zhengyu Gu | P4 | Closed | Fixed | b67 |
| JDK-8017840 | 7u45 | Zhengyu Gu | P4 | Closed | Fixed | b01 |
| JDK-8004383 | 7u40 | Zhengyu Gu | P4 | Closed | Fixed | b04 |
| JDK-8003874 | hs24 | Zhengyu Gu | P4 | Closed | Fixed | master |
The bug is discovered during backport.
The following assertion is intended to check that there is not more committed regions for the region to be released. It is not the case for partial releases, which can still have committed regions for the reserved regions that are not going to be released.
VMMemRegion* next_region = (VMMemRegion*)peek_next();
// should not have any committed memory in this reserved region
assert(next_region == NULL || !next_region->is_committed_region(), "Sanity check");
The following assertion is intended to check that there is not more committed regions for the region to be released. It is not the case for partial releases, which can still have committed regions for the reserved regions that are not going to be released.
VMMemRegion* next_region = (VMMemRegion*)peek_next();
// should not have any committed memory in this reserved region
assert(next_region == NULL || !next_region->is_committed_region(), "Sanity check");
- backported by
-
JDK-8003874 NMT: incorrect assertion in VMMemPointerIterator::remove_released_region method (memSnapshot.cpp)
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- relates to
-
-
- Closed
-