IJ07260: CRASHING BECAUSE OF CORRUPTED STACK-ALLOCATED OBJECT
Closed as program error.
Error Message: Assert from GC for an object not in heap memory . Stack Trace: The stderr of the JVM will contain output similar to the following: 07:56:05.803 0x140b6e00 j9mm.141 * Object not in heap 0000000042A22190 ** ASSERTION FAILED ** at MarkingScheme.cpp:366: ((false)) . This problems can happen on all platforms including X, Power and Z
The problem happens because of an optimization in the JIT Compiler allocates an object on the stack even when this object can be exposed to other threads.
The optimization has been fixed to correctly detect the object can be exposed to other threads and allocate it on the heap. . This APAR will be fixed in the following Java Releases: 7 R1 SR4 FP30 (22.214.171.124) 6 R1 SR8 FP70 (126.96.36.199) 7 SR10 FP30 (188.8.131.52) 8 SR5 FP20 (184.108.40.206) . Contact your IBM Product's Service Team for these Service Refreshes and Fix Packs. For those running stand-alone, information about the available Service Refreshes and Fix Packs can be found at: https://www.ibm.com/developerworks/java/jdk/
Reported component name
Reported component ID
NoSpecatt / Xsystem
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID