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

G1: mixed GC phase lasts for longer than it should

    XMLWordPrintable

Details

    • gc
    • b16
    • generic
    • generic
    • Not verified

    Backports

      Description

        It turns out that, under certain circumstances, G1 goes into "mixed GC" phase and does not come out of it in a timely manner. In some cases, several mixed GCs collect no old regions but are still considered "mixed". This, unfortunately, causes a serious issue: while we're in mixed GC mode we do not allow a new conc mark cycle to start. So, we have seen cases where a series of mixed GCs take place, the next cycle starts too late, and we end up with an evac failure / Full GC.

        Many thanks to Charlie Hunt for discovering this.

        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-2221494 G1: mixed GC phase lasts for longer than it should

            • P2 - Crashes, loss of data, severe memory leak.
            • Closed

            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-2221535 G1: mixed GC phase lasts for longer than it should

            • P2 - Crashes, loss of data, severe memory leak.
            • Closed
            relates to

            Enhancement - null JDK-7146246 G1: expose some of the -XX flags that drive which old regions to collect during mixed GCs

            • P3 - Major loss of function.
            • Closed

            Enhancement - null JDK-7145441 G1: collection set chooser-related cleanup

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

            Enhancement - null JDK-7146242 G1: alternative heuristic on deciding which old regions not to collect

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

            Activity

              People

                tonyp Tony Printezis
                tonyp Tony Printezis
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:
                  Imported:
                  Indexed: