<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">The recovery is large enough that it’s likely that class unloading allowed the collectors to recover as much as they did. Plus the space free before and after a compaction is the same. It’s just found in bigger chunks.<div><br></div><div>Regards,</div><div>Kirk</div><div><br><div><div>On Jul 15, 2014, at 3:31 AM, Elliot Barlas <<a href="mailto:Elliot.Barlas@citrix.com">Elliot.Barlas@citrix.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div fpstyle="1" ocsi="0" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word;"><div style="direction: ltr; font-family: Tahoma; font-size: 10pt;"><div>Alternatively, could my problem be due to fragmentation? Are there segments of free address space that are too small to use that could eventually be responsible for exhausting the old generation?</div><div><br></div><div>-Elliot</div></div></div></blockquote></div><br></div></body></html>