<br><font size=2 face="Courier New">>> CMS tries to project how early
to start a cycle based on past behavior. When there hasn't been much
data gathered about collections, the projection can just be wrong.</font>
<br><font size=2 face="Courier New">OK so it seems to be Q of how can I
mitigate this risk, i.e. is there anything I can do to influence this behaviour
such that the probability of such an incorrect call, by the collector,
is reduced? </font>
<br>
<br><font size=2 face="Courier New">Obviously ideally it would be possible
to eliminate the risk full stop but based on your reply it sounds like
I'd need to be able to guarantee that "this object really is not reachable
by anything that's in tenured" which really appears to equate to explicit
memory management.</font>
<br>
<br><font size=2 face="Courier New">Cheers</font>
<br><font size=2 face="Courier New">Matt</font>
<br><font size=2 face="Courier New"><br>
Matt Khan<br>
--------------------------------------------------<br>
GFFX Auto Trading<br>
Deutsche Bank, London<br>
</font>
<br>
<br>
<span style="font-family:sans-serif,helvetica; font-size:10pt; color:#000000">---<br>
<br>
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.<br>
<br>
Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.</span><br>