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

Implement ExitOnOutOfMemory and CrashOnOutOfMemory in HotSpot

    XMLWordPrintable

Details

    • b99

    Backports

      Description

        Right now, we have a flag "OnOutOfMemoryError=..." You can do a lot of things with it, for example -XX:OnOutOfMemoryError='kill -9 %p' to generate a core file on OOM.

        However, exiting and generating core files are two common cases that you may want to use when debugging. Instead of relying on command line tools (which is also harder on Windows), I suggest we implement two special cases. These were present in JRockit, so I suggest we use the same syntax (see http://docs.oracle.com/cd/E15289_01/doc.40/e15062/optionxx.htm )

        There two options in JRockit were:

        ExitOnOutOfMemory
        When you enable this option, the JVM exits on the first occurrence of an out-of-memory error. It can be used if you prefer restarting an instance of the JVM rather than handling out of memory errors.

        CrashOnOutOfMemoryError
        If this option is enabled, when an out-of-memory error occurs, the JVM crashes and produces text and binary crash files.

        Attachments

          Issue Links

            backported by

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8146083 Implement ExitOnOutOfMemory and CrashOnOutOfMemory in HotSpot

            • P3 - Major loss of function.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8146757 Implement ExitOnOutOfMemory and CrashOnOutOfMemory in HotSpot

            • P3 - Major loss of function.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8148019 Implement ExitOnOutOfMemory and CrashOnOutOfMemory in HotSpot

            • P3 - Major loss of function.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8149245 Implement ExitOnOutOfMemory and CrashOnOutOfMemory in HotSpot

            • P3 - Major loss of function.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8155341 Implement ExitOnOutOfMemory and CrashOnOutOfMemory in HotSpot

            • P3 - Major loss of function.
            • Resolved
            duplicates

            Enhancement - null JDK-8023218 Add option to generate core and hs_err files upon the occurrence out-of-memory error

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

            Bug - A problem which impairs or prevents the functions of the product. JDK-8218613 [TESTBUG] runtime/ErrorHandling tests are building incorrect testlibrary classes

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

            Bug - A problem which impairs or prevents the functions of the product. JDK-8274136 -XX:+ExitOnOutOfMemoryError calls exit while threads are running

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

            Activity

              People

                csahu Cheleswer Sahu (Inactive)
                mcastegr Mattis Castegren (Inactive)
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: