G1 tries to start a concurrent mark allocating a humongous object during initialization

XMLWordPrintable

    • Type: Bug
    • Resolution: Duplicate
    • Priority: P4
    • None
    • Affects Version/s: 26
    • Component/s: hotspot
    • gc

      If humongous allocation occurs during initialization, G1 will try to start a concurrent mark that will immediately fail and exit the VM.

      During that time, just rely on expanding the heap if necessary.

      Probably related to the InitialRAMPercentage changes

            Assignee:
            Unassigned
            Reporter:
            Thomas Schatzl
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: