IBM Support

IJ10792: CRASH DURING COMPILATION WITH STD::BAD_ALLOC ON X86

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: The JVM core dumps with the current thread
    running a compilation. The stderr output indicates the JVM
    crashed due to an std::bad_alloc exception. Java cores show an
    abort occurred.
    .
    Stack Trace: N/A
    .
    

Local fix

  • It may be possible to delay / reduce the frequency with which
    this issue is seen by increasing the amount of memory the JIT
    compiler is allowed to consume using the
    -Xjit:scratchSpaceLimit=<number in kbytes>. This does not
    correct the problem, but the higher memory limit makes it less
    likely a compilation will fail due to memory exhaustion.
    

Problem summary

  • During compilation of large methods, the compiler may run out of
    heap memory and abort a compilation. If this abort happens at a
    specific point in the code generator a destructor runs which
    attempts to allocate memory resulting in a double exception
    throw which automatically triggers a program abort/terminate
    from the C++ runtime.
    

Problem conclusion

  • The problem destructor has been modified to check if the
    destructor is running because of an exception or because of the
    normal end of an object life-time. If the destructor is run due
    to an exception, no attempt will be made to allocate memory
    allowing the normal memory exhaustion pathways to gracefully
    handle the compilation failure and allow the JVM to continue to
    run.
    .
    This APAR will be fixed in the following Java Releases:
       8   SR5  FP26    (8.0.5.26)
    .
    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

    IJ10792

  • Reported component name

    JIT

  • Reported component ID

    620700124

  • Reported release

    130

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-10-25

  • Closed date

    2018-11-02

  • Last modified date

    2018-11-06

  • 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

[{"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:
06 November 2018