-
Bug
-
Resolution: Duplicate
-
P3
-
6
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
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
- duplicates
-
JDK-6896603 CMS/GCH: incremental_collection_will_fail() should use more current data
- Closed
- relates to
-
JDK-6266735 intermittent extreme mutator slowdown in jbb runs with ParNew/DefNew
- Closed
-
JDK-6998802 ScavengeALot: assert(!gch->incremental_collection_failed()) failed: Twice in a row
- Closed