IJ05445: SEGMENTATION FAULT IN THE JIT JITWALKFRAME

APAR status

• Closed as program error.

Error description

• Error Message: A segmentation fault occurs during garbage
  collection.
  .
  Stack Trace: jitWalkFrame
  jitWalkStackFrames
  walkStackFrames
  GC_VMThreadStackSlotIterator::scanSlots
  MM_RootScanner::scanOneThread
  MM_RootScanner::scanThreads
  MM_CopyForwardScheme::scanRoots
  MM_CopyForwardScheme::workThreadGarbageCollect
  MM_ParallelDispatcher::slaveEntryPoint
  dispatcher_thread_proc2
  .
  

Local fix

• This issue can be worked around using the
  -Xjit:disableNewInstanceImplOpt option. Note that there may be a
  small performance impact depending on the application.
  

Problem summary

• The problem is caused when java/lang/Class.newInstance is called
  on primitive or array classes enough times to trigger
  java/lang/Class.newInstance to call to newInstanceImplThunk, a
  specially optimized method, which will use the constant pool of
  the class to be instantiate in its method meta data. Constant
  pool for primitive or array classes don't exist. Thus, a crash
  will happen when gc is walking the stack trying to dereference
  the constant pool of newInstanceImplThunk.
  

Problem conclusion

• The JIT has been updated to use a valid constant pool for
  primitive and array classes in newInstanceImplThunk.
  .
  This APAR will be fixed in the following Java Releases:
   7 SR10 FP25 (7.0.10.25)
   8 SR5 FP15 (8.0.5.15)
   7 R1 SR4 FP25 (7.1.4.25)
  .
  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