IBM Support

IV74405: CRASH IN JIT COMPILED CODE OR GC, OR MEMORY CORRUPTION

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • Error Message: Unhandled exception
    Type=Segmentation error vmState=0x00000000
    J9Generic_Signal_Number=00000004 Signal_Number=0000000b
    Error_Value=00000000 Signal_Code=00000001
    ...
    Compiled_method=com/google/inject/internal/InjectorImpl.callInCo
    ntext(Lcom/google/inject/internal/ContextualCallable;)Ljava/lang
    /Object;
    .
    Stack Trace: N/A
    .
    This problem has only been seen with the Google Guice framework
    for Java, where the problem usually manifested as a crash in the
    following method:
    com/google/inject/internal/InjectorImpl.callInContext(Contextual
    Callable<T>).
    

Local fix

  • The -Xjit:disableLocalCSE option will prevent this problem from
    occuring. Note that that this option will likely lead to reduced
    performance (up to 16% for cpu intensive applications).
    
    An alternative work around that will avoid the problem in the
    cases seen so far is
    
    -Xjit:disableInternalPointers
    
    This typically incurs less than a 2% performance penalty, but
    may not work in all theoretically possible cases of the problem.
    The best advice is to try disableInternalPointers first, and if
    that
    doesn't work then use the more conservative disableLocalCSE.
    

Problem summary

  • The JIT compiler performs an incorrect optimization that can
    lead to a stray pointer, which typically results in crashes but
    may also lead to memory corruption. This problem affects Java 6
    and later.
    

Problem conclusion

  • The JIT compiler has been fixed to perform the optimization
    correctly.
    .
    This APAR will be fixed in the following Java Releases:
       8    SR1 FP10  (8.0.1.10)
       7 R1 SR3 FP10  (7.1.3.10)
       7    SR9 FP20  (7.0.9.20)
       6 R1 SR8 FP15  (6.1.8.15)
       6    SR16 FP15 (6.0.16.15)
    .
    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 number

    IV74405

  • Reported component name

    JIT

  • Reported component ID

    620700124

  • Reported release

    130

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-06-20

  • Closed date

    2015-06-20

  • Last modified date

    2015-11-11

  • 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

  • R600 PSY

       UP

  • R260 PSY

       UP



Document information

More support for: Runtimes for Java Technology
Just In Time (JIT) Compiler

Software version: 130

Reference #: IV74405

Modified date: 11 November 2015