Am 06.04.2005 um 20:32 schrieb Andrew Piskorski:
On Wed, Apr 06, 2005 at 07:22:08PM +0200, Zoran Vasiljevic wrote:
As the matter of fact, the "zippy" memory allocator (what does "zippy" mean, btw?) seems rather broken. It is, since some time,
It means "fast", basically.
OK :-)
Interesting. A leak? Or some kind of pathological memory fragmentation? Does Valgrind say anything useful?
Well, technically speaking, this is not a leak per-se otherwise I would have spotted this one by purify-checking which i regulary do before releasing anything.
If you don't get any better/easier suggestions, for more black box testing, it might help to try the first version of Tcl that included the zippy allocator, and also the last version of AOLserver before the zippy allocator was removed from AOLserver and put into Tcl. Which of those cases do or do not exhibit the same problem should at least tell you if this is a recent bug introduced in Tcl, or if the same problem has always been there all along with the original zippy allocator in AOLserver.
This will require some time. I have tested Tcl from 8.4.5 until 8.5 and all seem to exibit the same behaviour. I somehow think that this has been always there...
Zoran
-- AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
