On Tue, 23 Nov 1999 01:46:04 -0600 (CST), Matthew Langford wrote: >Sorry, I didn't mean to send this. I meant to send the other message, Consider it not read. :-) Anyway, I'd like to apologize for the tone in my other message. I didn't mean to sound so harsh. But lots of people have been using MacPerl for years now, often on a daily basis, and I'm sure that such a blatant memory leak would have been noticed long ago. Now, a *small* memory leak could still go unnoticed, even for years. >There is still some memory loss in the realm >of an estimated 10K per iteration, That could be a memory leak, at least, partially. It could also be something else: while working, MacPerl constantly allocates and frees memory blocks. Freed blocks get reused, but as not all blocks are the same size, not all of it gets reused, and it is well possible that small memory fragments fall between the cracks, that they're too small to be reused, and these air pockets make the whole memory usage, after processing, larger than when simply reading in the structure into memory. It is a common problem with memory management. -- Bart. # ===== Want to unsubscribe from this list? # ===== Send mail with body "unsubscribe" to macperl-request@macperl.org