IBM Support

IV94682: ASSERTION OR CRASH DURING GARBAGE COLLECTION

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: A common symptom is for the Garbage Collector to
    report this assertion failure:
    "Object neither in heap nor stack-allocated"
    However a crash during Garbage Collection is also possible.
    .
    Stack Trace:
    .
    This problem can only happen if a java agent or debugger is
    attached. This problem can happen at all optimization levels
    except for noOpt.
    

Local fix

  • The problem can be avoided with the following Java command line
    option:
    -Xjit:disableInlining
    Note, this likely will significantly decrease performance.
    

Problem summary

  • When inlining a method into another method when the JRE has been
    launched with an agent or debugger attached, information
    necessary for the JIT compiler to keep track of Monitors was
    incorrectly propagated to one of the code paths which caused the
    JIT compiler to generate incorrect metadata used by Garbage
    Collection to keep track of objects in JIT compiled methods. The
    incorrect metadata for the Monitor caused the Garbage Collector
    to treat a register as if it contained the Monitor object when
    it did not, causing the Garbage Collector to throw an assertion
    error or crash.
    

Problem conclusion

  • The JIT compiler has been updated to correctly propagate
    information in the code paths specific to this problem.
    .
    This APAR will be fixed in the following Java Releases:
       7 R1 SR4 FP5   (7.1.4.5)
       8    SR4 FP5   (8.0.4.5)
    .
    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

    IV94682

  • Reported component name

    JIT

  • Reported component ID

    620700124

  • Reported release

    130

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-03-29

  • Closed date

    2017-03-29

  • Last modified date

    2017-03-29

  • 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

[{"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":"130","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
29 March 2017