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

MonitoringSupport_lock should be unconditionally initialized after 8304074

    XMLWordPrintable

Details

    • 21
    • b08
    • generic
    • generic

    Backports

      Description

        MonitoringSupport_lock is initialized only when UseG1GC is true, but JDK-8304074 uses it to implement getTotalThreadAllocatedBytes, which is available for all garbage collectors. While the current code sets UseG1GC regardless of which collector is specified, see FLAG_SET_ERGO_IF_DEFAULT(UseG1GC, true) in gcConfig.cpp, if G1 isn't included in the Hotspot build or Hotspot is not running on a server class machine, the lock will not be initialized. The lock's initialization should be unconditional.

        Attachments

          Issue Links

            backported by

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8313416 MonitoringSupport_lock should be unconditionally initialized after 8304074

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

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8321548 MonitoringSupport_lock should be unconditionally initialized after 8304074

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

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8321549 MonitoringSupport_lock should be unconditionally initialized after 8304074

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

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-8329782 MonitoringSupport_lock should be unconditionally initialized after 8304074

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

            Enhancement - null JDK-8304074 [JMX] Add an approximation of total bytes allocated on the Java heap by the JVM

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

            Enhancement - null JDK-8313202 MutexLocker should disallow null Mutexes

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

            Commit Commit openjdk/jdk8u-dev/af033c67

            Commit Commit openjdk/jdk11u-dev/3ea286a3

            Commit Commit openjdk/jdk17u-dev/bf7c2211

            Commit Commit openjdk/jdk21u/a892672f

            Commit Commit openjdk/jdk/a9d21c61

            Review Review openjdk/jdk8u-dev/393

            Review Review openjdk/jdk8u-dev/475

            Review Review openjdk/jdk11u-dev/2287

            Review Review openjdk/jdk17u-dev/1981

            Review Review openjdk/jdk21u/20

            Review Review openjdk/jdk/15028

            Activity

              People

                phh Paul Hohensee
                phh Paul Hohensee
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: