IV80362: ASSERT IN GC THAT AN OBJECT IS NEITHER IN HEAP NOR STACK-ALLOCAT ED

APAR status

• Closed as program error.

Error description

• Error Message: An assertion fails in ParallelScavenger.cpp with
  the message: Object neither in heap nor stack-allocated.
  .
  Stack Trace: N/A
  .
  This issue is by nature highly intermittent and will occur
  during startup. The method signature noted in the error message
  will always be a constructor of a class that gets loaded very
  early during startup. These will always be very primitive
  classes. e.g
  java/util/HashMap$Node.<init>(ILjava/lang/Object;Ljava/lang/Obje
  ct;Ljava/util/HashMap$Node;)V
  

Local fix

• Options that cause methods to be JIT compiled very early on
  could be a catalyst to this issue. Removing such options will
  help to alleviate the problem however there are no know
  workarounds.
  

Problem summary

• There is a race condition in the JIT compiler when making
  queries to the frontend. In certain situations metadata relating
  to the live stack objects for GC are not generated properly thus
  resulting in the GC assertion failing.
  

Problem conclusion

• The JIT has been updated to avoid this race condition and to
  properly generate the correct GC metadata.
  .
  This APAR will be fixed in the following Java Releases:
     8    SR2 FP10  (8.0.2.10)
  .
  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:

Fix information

• Fixed component name

  JIT

• Fixed component ID

  620700124

Applicable component levels

• R130 PSY

     UP