Am 05.04.2005 um 23:21 schrieb Stephen Deasey:
In a fresh, empty server (make runtest) memory use doesn't climb at
all (2.8MB res, 17MB virt).
Do you have any C modules loaded? Use ttrace?
Nothing! Just vanilla server. Have tried under Solaris. Same thing.
Then went and recompiled Tcl lib w/o the threaded allocator and
repeated the same test. Stable memory, i.e. no leaks. Compoiled
the threaded alloc again and repeated on Sol and Darwin and leak
appears again. Hm... You are testing under Linux?
On Apr 5, 2005 1:19 PM, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
Hey friends,
would you mind putting this in your nscp session and observe the
virtual
memory usage (e.g. with the top utility) in a separate window?
time {set t [ns_thread begin "set a 1"]; ns_thread join $t}
10000
I start with about 45MB server (startup) and end with 600MB after the
test!
I believe this is not a memleak per-se (i.e. one on e could catch with
Purify or such...). I believe this is a side-effect of the AOL memory
allocator which has been accepted by the Tcl core in threaded builds.
Anyways, this is absolutely unacceptable for us. I must do some
lobying
in the Tcl project to correct this somehow. This could explain some
memory-related problems in AS (and NS, consequently) reported by some
users. Alternbative could be to test the new Googled tmalloc (or
however
it is called)...
Cheers
Zoran
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real
users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
naviserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/naviserver-devel
