United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-7018286 G1: humongous allocation attempts should take the GC locker into account
JDK-7018286 : G1: humongous allocation attempts should take the GC locker into account

Details
Type:
Enhancement
Submit Date:
2011-02-09
Status:
Closed
Updated Date:
2011-04-24
Project Name:
JDK
Resolved Date:
2011-04-24
Component:
hotspot
OS:
generic
Sub-Component:
gc
CPU:
generic
Priority:
P4
Resolution:
Fixed
Affected Versions:
hs21
Fixed Versions:
hs21 (b08)

Related Reports
Backport:
Relates:
Relates:

Sub Tasks

Description
When G1 tries to do a humongous allocation but cannot find enough contiguous regions in the heap it will attempt to do a collection pause in case this pause reclaims enough contiguous space for the allocation to succeed. Currently, the attempt to do a collection pause does not check whether the GC locker is active or not and, if it's active, it will keep attempting to do back-to-back collection pauses which will be unsuccessful. Instead, it should stall until the GC locker becomes inactive.

                                    

Comments
SUGGESTED FIX

Simply stall while the GC locker is active, during a humongous allocation attempt, instead of keep trying to do pauses.
                                     
2011-02-09
EVALUATION

See Description.
                                     
2011-02-09
EVALUATION

http://hg.openjdk.java.net/jdk7/hotspot-gc/hotspot/rev/abdfc822206f
                                     
2011-03-30



Hardware and Software, Engineered to Work Together