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

Misleading G1 eager reclaim detail logging

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: P5 P5
    • 17
    • 11, 17
    • hotspot
    • gc
    • b26

      With gc+humongous (and eager reclaim on) the log output for found live regions looks as follows:

      Live humongous region <region-idx> object size <size> start <address> with remset <cardset-size> code roots <code-roots-size> is marked <is-marked> reclaim candidate <is-candidate> type array <is-type-array>

      There are some misleading values in the fields:

      <cardset-size> is always "0" at this point because for a long time now we always defer remset updates to the concurrent phase. (It also only contains actual number of references in the remset, not considering outstanding card set entries still to be refined).

      <is-candidate> is just wrong and always "false" here as it uses an internal table which entry is intentionally cleared if any reference has been found during gc

      Fix this; I think by moving the "Live" messages somewhere else and just making them "humongous object" messages both issues could be fixed.

            tschatzl Thomas Schatzl
            tschatzl Thomas Schatzl
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: