JDK-6261660 : CMS promotion failure & gc_locker induced GC malinteraction
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 6
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2005-04-26
  • Updated: 2010-12-02
  • Resolved: 2010-12-02
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 7
7Resolved
Related Reports
Duplicate :  
JDK-6896603 - CMS/GCH: incremental_collection_will_fail() should use more current data
Relates :  
JDK-6998802 - ScavengeALot: assert(!gch->incremental_collection_failed()) failed: Twice in a row
Relates :  
JDK-6266735 - intermittent extreme mutator slowdown in jbb runs with ParNew/DefNew
Description
This bug is a result of the changes in the most recent
previous putback to gc_baseline, specifically the
change here:

http://analemma.sfbay.sun.com/net/prt-archiver/data/archived_workspaces/main/gc_baseline/2005/20050420192605.ysr.gclocker_followup/workspace/webrevs/webrev-2005.04.21/src/share/vm/memory/defNewGeneration.cpp.sdiff.html


###@###.### 2005-04-26 19:22:49 GMT

Changed synopsis from:

10X slowdown in +UseSerialGC with GCBasher

to:

CMS promotion failure & gc_locker induced GC malinteraction
###@###.### 2005-04-26 21:20:36 GMT

###@###.### 2005-04-29 23:58:59 GMT
Comments
EVALUATION This is fixed as a side-effect of the recent changes in CR 6896603.
02-12-2010
EVALUATION For process reasons, this is now officially targeted to Dolphin.
27-10-2005
EVALUATION see comments section; note that this regression never made it out of gc_baseline. The regression is backed out in the putback 20050426123450.ysr.icms to gc_baseline. As a result the priority of the bug is being reduced, and the synopsis adjusted to reflect the remaining fix being tracked in this bug report. ###@###.### 2005-04-26 21:20:36 GMT
26-04-2005
WORK AROUND the workaround is to run with -Xmx and -Xms set to the same value so as not to run into the expansion anomaly/malinteraction with the new code. ###@###.### 2005-04-26 19:22:49 GMT
26-04-2005
SUGGESTED FIX a temporary fix is to backout the specific change shown in the description section. A better fix will be available in due time (i.e. at lower priority). ###@###.### 2005-04-26 19:22:49 GMT
26-04-2005