JDK-7181353 : Update error message to distinguish native OOM and java OOM in net
- Type: Enhancement
- Component: core-libs
- Sub-Component: java.net
- Affected Version: 7
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: linux
- CPU: x86
- Submitted: 2012-07-03
- Updated: 2013-06-26
- Resolved: 2012-07-25
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 |
|---|---|
7u40Fixed  |
8 b49Fixed |
Description
A DESCRIPTION OF THE REQUEST : This is a little enhancement to the error message in java/net/ on both windows and linux. The current out of memory error message is "heap allocation failed ", it makes some user confusing whether the OOM is in java heap or native. Please look at http://mail.openjdk.java.net/pipermail/net-dev/2012-July/004516.html for the discussion. JUSTIFICATION : The enhancement changes the error message from "heap allocation failed" to "Native heap allocation failed" , so it is clear the OOM is from native code.
Comments
|