Add tests which check that heap counters work as expected during Humongous allocations

XMLWordPrintable

    • Type: Enhancement
    • Resolution: Fixed
    • Priority: P3
    • 9
    • Affects Version/s: 9
    • Component/s: hotspot
    • None
    • gc
    • b107

      Humongous objects always take up a number of regions. If humongous object is smaller than one region it takes up the whole region. If a humongous object is larger than N regions and smaller than (N+1) regions it takes up (N+1) regions. No allocations are allowed in the free space (if any) of the last region.

       * free heap size should provide right values after humongous allocation.
       * amount of free regions should be right after humongous allocation.
       * amount of occupied regions should be right after humongous allocation.

            Assignee:
            Kirill Zhaldybin (Inactive)
            Reporter:
            Kirill Zhaldybin (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - 3 days
                3d
                Remaining:
                Remaining Estimate - 3 days
                3d
                Logged:
                Time Spent - Not Specified
                Not Specified