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

(bf) DirectByteBuffer constructor will leak if allocating Deallocator or Cleaner fails with OOME

    XMLWordPrintable

Details

    • b19

    Backports

      Description

        This was reported on nio-dev. In DirectByteBuffer, if allocating the Deallocator or Cleaner failed with OOME then the constructor will throw without releasing the memory that it has allocated.

        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-8308893 (bf) DirectByteBuffer constructor will leak if allocating Deallocator or Cleaner fails with OOME

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

            Commit Commit openjdk/jdk17u-dev/14779b1f

            Commit Commit openjdk/jdk/4cbac40d

            Review Review openjdk/jdk17u-dev/1396

            Review Review openjdk/jdk/10588

            Activity

              People

                bpb Brian Burkhalter
                alanb Alan Bateman
                Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: