RVM
  1. RVM
  2. RVM-440

Poisoned tests failing in finalizer thread

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.9.2
    • Fix Version/s: 3.0.1
    • Component/s: Runtime
    • Labels:
      None
    • Number of attachments :
      0

      Description

        Issue Links

          Activity

          Show
          Ian Rogers added a comment - Still present and effect DaCapo benchmarks too: http://jikesrvm.anu.edu.au/cattrack/results/rvmx86lnx32b.anu.edu.au/sanity/3587/FullAdaptivePoisoned/default/dacapo/lusearch/default/Output.txt
          Ian Rogers made changes -
          Field Original Value New Value
          Fix Version/s 2.9.4 [ 14162 ]
          David Grove made changes -
          Fix Version/s 3.0 [ 13530 ]
          Fix Version/s 2.9.4 [ 14162 ]
          David Grove made changes -
          Fix Version/s 3.0 [ 13530 ]
          Fix Version/s 3.0.1 [ 14378 ]
          Ian Rogers made changes -
          Link This issue relates to RVM-609 [ RVM-609 ]
          Ian Rogers made changes -
          Link This issue relates to RVM-633 [ RVM-633 ]
          Hide
          Ian Rogers added a comment -

          RVM-633 might have an effect on this issue.

          Show
          Ian Rogers added a comment - RVM-633 might have an effect on this issue.
          Show
          Ian Rogers added a comment - A more recent example of this failure: http://jikesrvm.anu.edu.au/cattrack/results/rvmx86lnx32b.anu.edu.au/sanity/4608/FullAdaptivePoisoned/default/SPECjbb2005/SPECjbb2005/default/Output.txt
          Hide
          Daniel Frampton added a comment -

          This should have been fixed with the new Finalization processing code.

          The previous code was unsafe in that it did not use the correct barriers when accessing the ready for finalize table. Closing to be reopened if the error shows up again.

          Show
          Daniel Frampton added a comment - This should have been fixed with the new Finalization processing code. The previous code was unsafe in that it did not use the correct barriers when accessing the ready for finalize table. Closing to be reopened if the error shows up again.
          Daniel Frampton made changes -
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Closed [ 6 ]

            People

            • Assignee:
              Daniel Frampton
              Reporter:
              Ian Rogers
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: