IJ07260: CRASHING BECAUSE OF CORRUPTED STACK-ALLOCATED OBJECT

APAR status

• Closed as program error.

Error description

• 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
  

Local fix

• -Xjit:disableEscapeAnalysis
  

Problem summary

• 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.
  

Problem conclusion

• 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 (7.1.4.30)
   6 R1 SR8 FP70 (6.1.8.70)
   7 SR10 FP30 (7.0.10.30)
   8 SR5 FP20 (8.0.5.20)
  .
  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/
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

• Fixed component name

  JIT

• Fixed component ID

  620700124

Applicable component levels