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

Bug in assignment operator of ReservedMemoryRegion

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • P4
    • 22
    • 22
    • hotspot
    • b11

    Description

      The assignment operator of ReservedMemoryRegion doesn't clear the initial committed regions list, so the original committed regions are still present after the assignment (and can even be outside of the new reserved region).

      As far as I can see this code is only triggered when a reserved region of a stack was not properly unregistered via ThreadStackTracker::delete_thread_stack() when a thread ends. So it should happen very rarely, if at all.

      Attachments

        Issue Links

          Activity

            People

              rschmelter Ralf Schmelter
              rschmelter Ralf Schmelter
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: