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

Shenandoah: should not block pacing reporters

    XMLWordPrintable

    Details

    • Subcomponent:
      gc
    • Resolved In Build:
      b02

      Backports

        Description

        After JDK-8247367, we are acquiring the _wait_monitor in ShenandoahPacer::report_internal. That runs into potential deadlocks with threads that are waiting on the same lock *and* safepointing at the same time, against the concurrent workers that want to report the progress before returning for subsequent safepoint.

        Also, this introduces latency/scalability hogs on fastpaths in concurrent mark.

        We are better off deferring the actual notification to a separate (periodic) task.

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                shade Aleksey Shipilev
                Reporter:
                shade Aleksey Shipilev
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved: