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

G1TraceReclaimDeadHumongousObjectsAtYoungGC only prints humongous object liveness output when there is at least one candidate humongous object

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Fixed
    • Icon: P4 P4
    • 9
    • 8u40, 9
    • hotspot
    • gc
    • b37

        The option G1TraceReclaimDeadHumongousObjectsAtYoungGC prints some information about live and dead humongous objects during early reclaim of humongous objects (JDK-8048180).

        However, it only does so when there is at least one humongous object candidate. This is problematic since this makes getting further information about humongous objects somewhat unreliable.

        The problem is that early in the GC phase, we check whether there are any candidates, and if not, skip the actual humongous reclaim phase (because there is nothing that can be reclaimed).

        It would be preferable that if G1TraceReclaimDeadHumongousObjectsAtYoungGC is set, do not skip the humongous reclaim phase even if it cannot reclaim anything, but at least print the information.

        Also, add humongous object size to the output.

        This would help analyzing for JDK-8048179.

              sangheki Sangheon Kim
              tschatzl Thomas Schatzl
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: