G1 starts a concurrent mark when allocating humongous objects during initialization

XMLWordPrintable

    • gc
    • b05

        Tests could fail with
           "Error occurred during initialization of VM
            GC triggered before VM initialization completed. Try increasing NewSize, current value 1331K."

          when running in AOT mode using different GC in training and production runs.

        The issue is seen at least when ZGC was used in training run and G1 GC was used in production run.

        As found below by [~eosterlund], this is because of G1's policy to preemptively start concurrent marking during humongous object allocation. The VM may not be ready to perform a GC this time. Simply do not issue the GC at that time.

        Most likely related to JDK-8371986 where the default value of InitialRAMPercentage has been removed/set to 0.

              Assignee:
              Thomas Schatzl
              Reporter:
              Ekaterina Pavlova
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: