JDK-6975964 : G1: print out a more descriptive message for evacuation failure when +PrintGCDetails is set
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: hs19
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2010-08-10
  • Updated: 2013-09-18
  • Resolved: 2011-04-23
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 6 JDK 7 Other
6u21pFixed 7Fixed hs19Fixed
Description
When an evacuation failure occurs in G1, G1 outputs "--" or "(evacuation failed)" in the GC log. Some users are worried when they read than something "fails" in the log. We should rephrase it.

Thanks to Jon Masamitsu for bringing this up.

Comments
EVALUATION http://hg.openjdk.java.net/jdk7/hotspot-gc/hotspot/rev/b63010841f78
17-08-2010

PUBLIC COMMENTS On this change I'll piggy-back a very small additional change which is to remove the printing of the duration of the mark closure when marking is on. I.e., this [GC pause (young)Mark closure took 5.72 ms. , 0.07517200 secs] will look like this after the change: [GC pause (young), 0.07517200 secs] The mark closure output was messing up the parsing of the logs.
17-08-2010

PUBLIC COMMENTS Instead of evacuation failure we'll use the word "overflow". So, "evacuation failure" becomes "to-space overflow". Additionaly, when +G1PrintHeapRegions is set we currently print out "evacuation failed in heap region...". We'll change that to "overflow in heap region...".
11-08-2010

EVALUATION See Description.
10-08-2010