IJ07440: JVM CRASH IN JIT-COMPILED CODE DUE TO MISSING TYPE CHECK

APAR status

• Closed as program error.

Error description

• Error Message: Segmentation error.
  .
  Stack Trace:
  One method that is known to hit this problem is
  org/apache/webbeans/container/InjectionResolver.implResolveByTyp
  e()
  .
  

Local fix

• The problem can be avoided by passing
  -Xjit:disableLoopVersioner,disableLoopAliasRefiner,disableOpts={
  loopSpecializer} for Java 8, or
  -Xjit:disableLoopVersioner,disableOpts={loopSpecializer} for
  Java 7.1, 7.0, or 6.1. These options are likely to degrade
  performance, but they can be limited to problematic methods.
  

Problem summary

• The JIT compiler can hoist loads from memory out of a loop. Such
  a load may require a dynamic type check to establish that it is
  safe to perform. In certain cases the compiler could omit a
  necessary type check, producing output code that is not type
  safe. This problem is more likely to occur when running with
  -Xtune:virtualized.
  

Problem conclusion

• The JIT compiler has been modified to generate the necessary
  type checks in these cases.
  .
  This APAR will be fixed in the following Java Releases:
   8 SR5 FP17 (8.0.5.17)
   7 SR10 FP30 (7.0.10.30)
   6 R1 SR8 FP70 (6.1.8.70)
   7 R1 SR4 FP30 (7.1.4.30)
  .
  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