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

Remove GCLockerInvokesConcurrent

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Fixed
    • P4
    • 14
    • 14
    • hotspot
    • gc
    • 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

          csr for

          CSR - null JDK-8233877 Remove GCLockerInvokesConcurrent

          • P4 - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JDK-8192647 GClocker induced GCs can starve threads requiring memory leading to OOME

          • P3 - Major loss of function.
          • Open

          Enhancement - null JDK-8232365 Implementation for JEP 363: Remove the Concurrent Mark Sweep (CMS) Garbage Collector

          • P4 - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JDK-6919638 CMS: ExplicitGCInvokesConcurrent misinteracts with gc locker

          • P3 - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JDK-8233279 G1: GCLocker GC with +GCLockerInvokesConcurrent spins while cycle in progress

          • P4 - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          JEP - Java Enhancement Proposal JDK-8229049 JEP 363: Remove the Concurrent Mark Sweep (CMS) Garbage Collector

          • P2 - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: