JDK-8003487 : NMT: incorrect assertion in VMMemPointerIterator::remove_released_region method (memSnapshot.cpp)
- Type: Bug
- Component: hotspot
- Sub-Component: runtime
- Affected Version: hs25
- Priority: P4
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2012-11-15
- Updated: 2014-06-26
- Resolved: 2012-11-16
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 7 | JDK 8 | Other |
|---|---|---|
7u40Fixed  |
8Fixed |
hs24Fixed |
Related Reports
|
Relates :
|
Description
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");