DirtyCardToOopClosure scanning one object too many.

XMLWordPrintable

    • Type: Bug
    • Resolution: Other
    • Priority: P3
    • 1.4.0
    • Affects Version/s: 1.4.0
    • Component/s: hotspot
    • None
    • gc
    • beta2
    • generic
    • generic


      We're scanning one object too many in DirtyCardToOopClosure.
      This means we need to test that we're not rescanning an object in
      DefNewGeneration's ScanClosure and FastScanClosure -- when this
      is fixed, that test can be changed to an assert.

      See also 4461854.

      This can be seen when running specjvm98, first failure occurs in jess:

            Assignee:
            Jane Loizeaux (Inactive)
            Reporter:
            Jane Loizeaux (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: