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

Incorrect GC log output: "concurrent mode failure" shown when heap histo is generated with SIGQUIT

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: P4 P4
    • 6
    • 6
    • hotspot
    • gc
    • b92
    • generic
    • generic

      This is an extract from a GC log that was sent to us

      1454.986: [CMS (concurrent mode failure): 9224K->10063K(843776K), 0.8197855 secs] 151890K->10063K(1014464K), [CMS Perm : 17494K->17270K(17536K)], 0.8207795 secs]
      num #instances #bytes class name
      --------------------------------------
        1: 38314 4811808 <no name>
        2: 60969 2784112 <symbolKlass>
        3: 38314 2762744 <methodKlass>
        4: 35377 1981112 java.nio.DirectByteBuffer
        5: 3480 1918464 <constantPoolKlass>
        6: 18353 1578184 [C
        ...

      A SIGQUIT was sent to the JVM to get a heap histogram. Before that heap histogram could be calculated, a Full GC was done. The Full GC was flagged as "concurrent mode failure" which is incorrect as there's not even a GC cycle running at the time.

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

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: