United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-6728271 G1: Cleanup G1CollectedHeap::get_gc_alloc_regions()
JDK-6728271 : G1: Cleanup G1CollectedHeap::get_gc_alloc_regions()

Details
Type:
Bug
Submit Date:
2008-07-22
Status:
Resolved
Updated Date:
2010-04-04
Project Name:
JDK
Resolved Date:
2009-04-02
Component:
hotspot
OS:
generic
Sub-Component:
gc
CPU:
generic
Priority:
P5
Resolution:
Fixed
Affected Versions:
7
Fixed Versions:
hs15 (b04)

Related Reports
Backport:
Backport:
Backport:
Backport:
Relates:
Relates:

Sub Tasks

Description
In G1CollectedHeap::get_gc_alloc_regions() we should either:
a. Handle aliases correctly and not call set_gc_alloc_region() twice for a region or
b. We could just eliminate the gc alloc region reuse code. Because currently gc alloc regions are discarded after the collection.

                                    

Comments
SUGGESTED FIX

See Evaluation.
                                     
2009-03-13
EVALUATION

This will be piggybacked on the fix for 6604422. The changes of that CR ensure that only one old region (and not survivor regions) will be retained across GCs, which makes the problem described here (calls to set_gc_alloc_region() multiple times on the same region) not possible. So, I don't think there's much point in dealing with the problem directly right now. I've added a couple of asserts to catch the problem if in the future this assumption changes.
                                     
2009-03-13
EVALUATION

http://hg.openjdk.java.net/jdk7/hotspot-gc/hotspot/rev/6c4cea9bfa11
                                     
2009-03-16



Hardware and Software, Engineered to Work Together