JDK-8026698 : Incorrect error handling in Metaspace::allocate
- Type: Bug
- Component: hotspot
- Sub-Component: gc
- Affected Version: hs25
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2013-10-16
- Updated: 2013-10-29
- Resolved: 2013-10-18
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 8 | Other |
|---|---|
8Fixed  |
hs25Fixed |
Related Reports
|
Relates :
|
Description
When an allocation has failed and we call report_metadata_oome we should be calling it with CHECK_NULL. The current code just passes THREAD an a comment claims that the next line is unreachable. I = M (incorrect error handling) L = M (only happens on failed allocations) W = M (avoid allocation failures)
Comments
|