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

Remove GCLockerInvokesConcurrent

    Details

    • Type: Enhancement
    • Status: Resolved
    • Priority: P4
    • Resolution: Fixed
    • Affects Version/s: 14
    • Fix Version/s: 14
    • Component/s: hotspot
    • Labels:
    • Subcomponent:
      gc
    • Resolved In Build:
      b24

      Description

      The product option GCLockerInvokesConcurrent was introduced by JDK-6919638 as part of fixing a bad interaction between GCLocker GCs and +ExplicitGCInvokesConcurrent for CMS. (A GCLocker GC would wait for the concurrent collection to complete, which was not desirable.)

      It was added to retain support for requesting that GCLocker GCs would (attempt to) trigger a concurrent collection cycle, but separate it from +ExplicitGCInvokesConcurrent. Even at the time it was noted that this might be a suboptimial policy.

      This option was only used by G1 and CMS. CMS has been removed (JDK-8232365). G1 had a serious bug until very recently (JDK-8233279, 2019-11-13), and even with that fixed the feature remains suboptimal. Better to just remove it.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                kbarrett Kim Barrett
                Reporter:
                kbarrett Kim Barrett
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: