IBM Support

IV50697: INCORRECTLY INITIALIZED FIELD

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: This can cause an assert in the garbage
    collector:
    00007F236070E900: Object neither in heap nor stack-allocated in
    thread Pooled Thread #226 running
    tests.com.ibm.jtc.bdtest.RBPTestSplit042
    00007F236070E900: O-Slot=00007F234744E8B8
    00007F236070E900: O-Slot value=00000000D4F6DCA8
    00007F236070E900: PC=00007F2335DCD57E
    00007F236070E900: framesWalked=3
    00007F236070E900: arg0EA=00007F23B4196888
    00007F236070E900: walkSP=00007F23B4196828
    00007F236070E900: literals=0000000000000010
    00007F236070E900: jitInfo=00007F23B93767D8
    00007F236070E900: method=00007F266C71D1C0
    (java/math/BigInteger.intValue()I) (JIT)
    00007F236070E900: stack=00007F23B41903B0-00007F23B41973F0
    Note that the "O-Slot value" (00000000D4F6DCA8) is half zeros,
    and half pointer data.
    If this goes undetected by the garbage collector, it can cause
    an impossible NullPointerException on Linux or Windows, or just
    a crash in jitted code on other platforms.  Typical example:
    java.lang.NullPointerException
      at java.math.BigInteger.getInt(BigInteger.java:3063)
    (In this case, BigInteger.java:3063 is a line of code that
    cannot possibly throw a NPE.)
    .
    Stack Trace: N/A
    .
    Observed only with -Xcheck:jni.  It is not known whether this
    option is required to trigger the failure, but the failure was
    never observed without it.
    

Local fix

  • Stop using -Xcheck:jni.  If that doesn't help,
    -Xjit:disableInlining should make the failure stop, at a
    significant cost in performance.
    

Problem summary

  • The Inliner optimization used inconsistent information when
    determining the number of arguments for a call to a JNI native
    method, causing the optimizer to crash.
    

Problem conclusion

  • This defect will be fixed in:
    6.0.1 SR7
    7.0.0 SR6
    .
    Inliner was fixed to compute the correct number of arguments for
    JNI calls.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV50697

  • Reported component name

    JIT

  • Reported component ID

    620700124

  • Reported release

    260

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-10-10

  • Closed date

    2013-10-11

  • Last modified date

    2013-10-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

  • R260 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSC9HBA","label":"Just In Time (JIT) Compiler"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"260","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
11 October 2013