-
Bug
-
Resolution: Fixed
-
P3
-
hs25
-
b56
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8027514 | 8 | Mikael Gerdin | P3 | Resolved | Fixed | b114 |
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)
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)
- backported by
-
JDK-8027514 Incorrect error handling in Metaspace::allocate
- Resolved
- relates to
-
JDK-8024547 MaxMetaspaceSize should limit the committed memory used by the metaspaces
- Closed