Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8227309

Handle OOM when rematerializing objects less surprising

    XMLWordPrintable

Details

    • Bug
    • Status: Open
    • P3
    • Resolution: Unresolved
    • 8u40, 11, 12, 13, 14
    • tbd
    • hotspot

    Description

      In JDK-8226536 we did a test fix to a test that provokes OOM and runs into problem when failing to rematerialize scalar replaced objects in deoptimization.

      That bug report contains reproducers and thoughts. Some of the issues encountered:
      * The OOM is thrown from an unexpected place
      * The finally block is not run

      In the future with value types this situation might become more common. We need to decide how we want to handle this.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. JDK-8270010 Handling of failed reallocation of scalar-replaced objects skips some exception handlers

          • P3 - Major loss of function.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JDK-8226536 Catch OOM from deopt that fails rematerializing objects

          • P2 - Crashes, loss of data, severe memory leak.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JDK-8273095 vmTestbase/vm/mlvm/anonloader/stress/oome/heap/Test.java fails with "wrong OOME"

          • P3 - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JDK-8269849 vmTestbase/gc/gctests/PhantomReference/phantom002/TestDescription.java failed with "OutOfMemoryError: Java heap space: failed reallocation of scalar replaced objects"

          • P4 - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JDK-8289764 gc/lock tests failed with "OutOfMemoryError: Java heap space: failed reallocation of scalar replaced objects"

          • P4 - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JDK-8270010 Handling of failed reallocation of scalar-replaced objects skips some exception handlers

          • P3 - Major loss of function.
          • Closed

          Enhancement - null JDK-8066400 Reserve memory for OOME exception processing during deoptimization

          • P3 - Major loss of function.
          • Open

          Activity

            People

              Unassigned Unassigned
              neliasso Nils Eliasson (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated: