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

G1CH::_expand_heap_after_alloc_failure is no longer needed

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Fixed
    • Icon: P4 P4
    • 18
    • 18
    • hotspot
    • gc
    • b11

      G1CollectedHeap::_expand_heap_after_alloc_failure was introduced by JDK-7113006 (fixed in 2012) to eliminate repeated expansion attempts and the associated logging once expansion had failed, resulting in evacuation failure.

      However, since then (2015) we have JDK-8003237, which cuts off the appropriate slow path entirely on evacuation failures. That means we won't hit the case where _expand_heap_after_alloc_failure is false more than once. (It can be hit once because survivor space and old space are tracked as full separately.)

            iwalulya Ivan Walulya
            kbarrett Kim Barrett
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: