<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">Thanks Thomas for looking at it.</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">I had completely missed the "To-space exhausted" message (was looking for promotion / evacuation failure):</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><p style="margin: 0px; font-size: 11px; line-height: normal; font-family: Menlo;"><span style="font-variant-ligatures: no-common-ligatures">[1.194s][info][gc ] GC(3) To-space exhausted</span></p><div><br></div></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">I kinda prefer “To-space exhausted” I have to say (maybe, it’s not always promotion to old that fails). I’d vote to leave it as is. If we want consistency, maybe we change the “Promotion failed” messages to “To-space exhausted” (on a separate CR, though)?</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">Tony</div> <br><p class="airmail_on">On April 19, 2016 at 12:34:50 PM, Thomas Schatzl (<a href="mailto:thomas.schatzl@oracle.com">thomas.schatzl@oracle.com</a>) wrote:</p> <blockquote type="cite" class="clean_bq"><span><div><div></div><div>Hi,
<br>
<br>On Wed, 2016-04-13 at 09:06 -0400, Tony Printezis wrote:
<br>> Hi all,
<br>>
<br>> First, thanks to Thomas for pushing the patch for 8152312. Here’s a
<br>> new webrev with the refactored G1 changes:
<br>>
<br>> http://cr.openjdk.java.net/~tonyp/8151556/webrev.1/
<br>>
<br>
<br> looks good to me. Testing (jprt, vm.gc testlist) looks fine.
<br>
<br>> Related question: Does G1 report on the GC log that an evacuation
<br>> failure has occurred, the same way all the other GCs report promotion
<br>> failures?
<br>>
<br>> [6.319s][info][gc,promotion ] Promotion failed
<br>>
<br>> Should I add an extra message as part of this change?
<br>
<br>G1 reports promotion failure by indicating this in the GC kind message
<br>(like "Pause Young (to-space-exhausted)").
<br>
<br>It would be nice to add this message to get consistent output for all
<br>gcs though.
<br>
<br>Thanks,
<br> Thomas
<br>
<br></div></div></span></blockquote> <div id="bloop_sign_1461158155916125184" class="bloop_sign"><div style="font-family:helvetica,arial;font-size:13px"><div>-----</div><div><br></div><div>Tony Printezis | JVM/GC Engineer / VM Team | Twitter</div><div><br></div><div>@TonyPrintezis</div><div><a href="mailto:tprintezis@twitter.com">tprintezis@twitter.com</a></div><div><br></div></div></div></body></html>