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.
> time {set t [ns_thread begin "set a 1"]; ns_thread join $t} 10000
>
> and keep an eye on a "top" utility in some other window, you will see AS
> happilly chewing up your memory and growing fatter and fatter.
> To make sure this isn't related to AS directly, I went and did that in
> the plain tclsh with threading extension loaded. Same thing.
Interesting. A leak? Or some kind of pathological memory
fragmentation? Does Valgrind say anything useful?
> OK. Now, please, whoever wrote this "zippy" (whatever that means)
> can you please see what is going on? Or at least give me some hint
> where to start digging. I need to get rid of this "side effect"....
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.
--
Andrew Piskorski <[EMAIL PROTECTED]>
http://www.piskorski.com/
--
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.
