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

JRE fails to start by only specifying -XX:+AggressiveHeap

XMLWordPrintable

    • gc
    • x86_64
    • generic

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


      FULL OS VERSION :
      Linux acme 3.13.0-44-generic #73-Ubuntu SMP Tue Dec 16 00:22:43 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux


      EXTRA RELEVANT SYSTEM CONFIGURATION :
      No env vars to specify java options

      A DESCRIPTION OF THE PROBLEM :
      Only specifying -XX:+AggressiveHeap prevents the JRE from starting.

      I am aware of the release note "JDK-8173678 : Release Note: With UseG1GC, specifying -XX:ParallelGCThreads=0 is no longer allowed".

      But I think it does not apply since I am not trying to use G1GC.



      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 :
      Execute
      java -XX:+AggressiveHeap <anyclass>

      You will see errors message
      The Parallel GC can not be combined with -XX:ParallelGCThreads=0

      EXPECTED VERSUS ACTUAL BEHAVIOR :
      The JDK to start
      REPRODUCIBILITY :
      This bug can be reproduced always.

      ---------- BEGIN SOURCE ----------
      public class a
      {
          public static void main( String[] args )
          {
              System.out.println( "hello" );
          }
      }

      ---------- END SOURCE ----------

      CUSTOMER SUBMITTED WORKAROUND :
      I was able to get my JRE to start by specifying -XX:ParallelGCThreads=1 before -XX:+AggressiveHeap.
      But I don't think this is ideal since from what I can tell the JRE used to decide how many threads to use based on the number of threads and memory in the system.

            fmatte Fairoz Matte
            webbuggrp Webbug Group
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: