i think there is at least 20 years of lit on "how to cope with memory exhaustion". in limbo almost any chunk of code can exhaust the heap, throws an exception and the errant dudes get cleaned up. i've only seen it in torture tests but no crashes ... just culprits.
brucee On 6/10/06, Paul Lalonde <[EMAIL PROTECTED]> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 9-Jun-06, at 5:59 PM, [EMAIL PROTECTED] wrote: > > however, i have yet to see a small allocation fail without the > system being pretty broken. and my conclusion is that preemtive > strikes against failures that should not happen on a sane system > may cause more harm than good. I have seen allocations that are *supposed* to be small fail - some of the most precious results are in the middle of runs of code that's far from what you or I would call production-ready. There's plenty of cases of relatively fragile software doing smart things with partial results when a programmer error occurs; when partial runs have value you save the result... Paul -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFEih08pJeHo/Fbu1wRAkBsAJ9Mj7i0aJnrnMDhJWI/mtII0ScPRgCgoDM+ mLfgd72HPUb5NbMb6LH59m8= =6RkZ -----END PGP SIGNATURE-----
