Hi,
Before I start to dig and make fire in Tcl project, I just wanted to
check
this here...
As the matter of fact, the "zippy" memory allocator (what does "zippy"
mean, btw?)
seems rather broken. It is, since some time, part of the Tcl and it is
turned on
per-default if compiling with threads enabled.
Now, if you use something like Tcl 8.4.6 or later in your AS instance
and do
this for example, from the nscp session:
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.
Then, you go, throw away -DUSE_THREAD_ALLOC=1 from the Tcl makefile,
recompile again and try again... See? All seems suddenly fine.
I have made some tests on Solars, Darwin and Linux and it does not seem
to
have any influence which OS you use (understandably, as I expected).
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"....
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.
