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

HotSpot VM fails to start when AggressiveHeap is set

    Details

    • Subcomponent:
      gc
    • Introduced In Build:
      b131
    • Introduced In Version:
      9
    • Resolved In Build:
      b168
    • CPU:
      generic
    • OS:
      generic
    • Verification:
      Verified

      Backports

        Description

        FULL PRODUCT VERSION :
        java version "1.8.0_131"
        Java(TM) SE Runtime Environment (build 1.8.0_131-b11)
        Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode)

        FULL OS VERSION :
        Mac OS X Sierra 10.12.4
        Darwin ID-PC14001.local 16.5.0 Darwin Kernel Version 16.5.0: Fri Mar 3 16:52:33 PST 2017; root:xnu-3789.51.2~3/RELEASE_X86_64 x86_64

        A DESCRIPTION OF THE PROBLEM :
        When specifying -XX:+AggressiveHeap as JVM argument the VM now aborts with an error message . This used to work perfectly fine in all previous versions of the JRE/JDK

        THE PROBLEM WAS REPRODUCIBLE WITH -Xint FLAG: Yes

        THE PROBLEM WAS REPRODUCIBLE WITH -server FLAG: Yes

        REGRESSION. Last worked in version 8u121

        STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
        In the simplest form even this command line aborts
        "java -XX:+AggressiveHeap -version" with error message
        "The Parallel GC can not be combined with -XX:ParallelGCThreads=0"

        In previous versions this simple cmd line would print the version. But any other combination doesn't work either.

        Additionally trying to use PrintFlagsFinal to check the actual value still causes the error.
        Many products ship with the setting in some config file out of the box (as do our own when set to production level during install)

        PrintFlagsFInal confirms that it was using 8 threads on my machine prior to u131.

        EXPECTED VERSUS ACTUAL BEHAVIOR :
        That the virtual machine starts up with AggressiveHeap enabled without error
        ERROR MESSAGES/STACK TRACES THAT OCCUR :
        "The Parallel GC can not be combined with -XX:ParallelGCThreads=0"

        REPRODUCIBILITY :
        This bug can be reproduced always.

        ---------- BEGIN SOURCE ----------
        java -XX:+AggressiveHeap -version
        ---------- END SOURCE ----------

        CUSTOMER SUBMITTED WORKAROUND :
        You can work arround this by explicitly specifying a value for ParallelGCthreads only if that argument is earlier in the argument list than AggressiveHeap.

        But having to figure out why certain services/java based apps no longer start and having to edit the config files in the right location and order is annoying at best.

          Issue Links

            Activity

              People

              • Assignee:
                kbarrett Kim Barrett
                Reporter:
                webbuggrp Webbug Group
              • Votes:
                0 Vote for this issue
                Watchers:
                10 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: