United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-7168294 G1: Some Full GCs incorrectly report GC cause as "No GC"
JDK-7168294 : G1: Some Full GCs incorrectly report GC cause as "No GC"

Details
Type:
Bug
Submit Date:
2012-05-11
Status:
Closed
Updated Date:
2013-06-11
Project Name:
JDK
Resolved Date:
2012-05-23
Component:
hotspot
OS:
generic
Sub-Component:
gc
CPU:
generic
Priority:
P4
Resolution:
Fixed
Affected Versions:
8
Fixed Versions:
hs24 (b11)

Related Reports
Backport:
Backport:

Sub Tasks

Description
During a recent G1 TOI, a GC log entry for a full GC was shown:

9.239: [Full GC (No GC) 128M->125M(128M), 9.0804393 secs]

which is showing "No GC" as the cause.

It turns out that this is incorrect and we have path in G1 where we do not set the GC cause.

                                    

Comments
SUGGESTED FIX

Set the GC cause using an instance of the GCCauseSetter class.
                                     
2012-05-11
EVALUATION

GC cause not being set when a full GC is invoked from VM_G1CollectForAllocation
                                     
2012-05-11
EVALUATION

http://hg.openjdk.java.net/hsx/hotspot-gc/hotspot/rev/1096fc5a52eb
                                     
2012-05-15
EVALUATION

http://hg.openjdk.java.net/lambda/lambda/hotspot/rev/1096fc5a52eb
                                     
2012-06-29
Verified by Mikael Gerdin in HS24 b11, 8 b39
                                     
2013-06-11
EVALUATION

http://hg.openjdk.java.net/hsx/hotspot-rt/hotspot/rev/1096fc5a52eb
                                     
2012-05-26



Hardware and Software, Engineered to Work Together