JDK-7046490 : Preallocated OOME objects should obey Throwable stack trace protocol
- Type: Bug
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 7u2
- Priority: P3
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2011-05-19
- Updated: 2011-11-25
- Resolved: 2011-11-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 | Other |
|---|---|---|
7u2Fixed  |
8Fixed |
hs22Fixed |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
After a series of changes culminating in 6998871, Throwable objects were allowed to be brought into being in an immutable state after construction. The objects created by the Throwable constructors and by readObject obey a documented protocol around the setting of the various fields to indicate mutability or immutability. Any Throwable objects directly created by the VM should also obey this protocol.
Comments
|