Details
-
Bug
-
Resolution: Fixed
-
P3
-
hs25
-
b62
Backports
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8001099 | hs25 | Nils Loodin | P3 | Closed | Fixed | b06 |
Description
This would be good when you are monitoring the VM, and causing allocations to occur as a result of this. In this case, you don't want a running production-vm to die because you asked it to print out its stacktrace for you.
When using CHeap-based classes, we can use the std::nothrow-syntax today to allocate objects but not dying on failure. However, not when using Resource objects. This should be fixed.
When using CHeap-based classes, we can use the std::nothrow-syntax today to allocate objects but not dying on failure. However, not when using Resource objects. This should be fixed.
Attachments
Issue Links
- backported by
-
JDK-8001099 It should be possible to allocate memory without the VM dying on failure.
- Closed