JDK-7018286 : G1: humongous allocation attempts should take the GC locker into account
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: hs21
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2011-02-09
  • Updated: 2013-09-18
  • Resolved: 2011-04-24
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 Other
7Fixed hs21Fixed
Related Reports
Relates :  
JDK-7005799 - G1: nsk/regression/b6186200 fails with OOME
Relates :  
JDK-7033292 - G1: nightly failure: Non-dirty cards in region that should be dirty
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
EVALUATION http://hg.openjdk.java.net/jdk7/hotspot-gc/hotspot/rev/abdfc822206f
30-03-2011
SUGGESTED FIX Simply stall while the GC locker is active, during a humongous allocation attempt, instead of keep trying to do pauses.
09-02-2011
EVALUATION See Description.
09-02-2011