United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: 7046490 Preallocated OOME objects should obey Throwable stack trace protocol
7046490 : Preallocated OOME objects should obey Throwable stack trace protocol

Details
Type:
Bug
Submit Date:
2011-05-19
Status:
Closed
Updated Date:
2011-11-25
Project Name:
JDK
Resolved Date:
2011-11-25
Component:
hotspot
OS:
generic
Sub-Component:
runtime
CPU:
generic
Priority:
P3
Resolution:
Fixed
Affected Versions:
7u2
Fixed Versions:
hs22

Related Reports
Backport:
JDK-2213965 - Preallocated OOME objects should obey Throwable stack trace protocol
Backport:
JDK-2213561 - Preallocated OOME objects should obey Throwable stack trace protocol
Relates:
JDK-7045138 - OutOfMemoryError thrown without stack trace in jdk7-b142
Relates:
JDK-6998871 - Support making the Throwable.stackTrace field immutable

Sub Tasks

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
EVALUATION

See main CR
2011-09-14 
EVALUATION

http://hg.openjdk.java.net/hsx/hotspot-main/hotspot/rev/0b80db433fcb
2011-07-27 
EVALUATION

http://hg.openjdk.java.net/hsx/hotspot-rt/hotspot/rev/0b80db433fcb
2011-07-22 
EVALUATION

When the VM sets the backtrace into a pre-allocated OOME it should update the Java level stackTrace field to be UNASSIGNED_STACK as-if the constructor had been invoked.
2011-05-19


Hardware and Software, Engineered to Work Together