Am 06.04.2005 um 21:07 schrieb Stephen Deasey:
I'm looking in /proc/$PID/maps and yes, the tcl (8.4.6) I have
installed under /opt/tcl/lib/libtcl8.4.so is the only one linked in.
From the command prompt that results from running 'make runtest', no
leaks. From the ncsp port, no leaks. I'm looking directly at
/proc/$PID/status, vm is stable at ~20MB, res ~3MB.
Absolutely strange.
However! Running /opt/tcl/bin/tclsh8.4 *does* leak memory. Not as
quickly as the test I did with 8.5, though.
Aha... meaning somebody broke the thing when moving to Tcl?
Thinking about this, it doesn't seem like an error in strategy of the
zippy ('quick') allocator, i.e. fragmentation. Looks like cleanup on
thread exit is just buggy.
This is what I thought as well and did some gdb-ing, but it all seems
fine.
There have been some changes in this area of Tcl. Just a very quick
scan brought up this, which is tagged 8.4.7:
http://cvs.sourceforge.net/viewcvs.py/tcl/tcl/unix/tclUnixThrd.c?
r1=1.23.2.6&r2=1.23.2.7
Correct threaded obj allocator to
fully cleanup on exit and allow for
reinitialization. [Bug #736426]
(mistachkin, kenny)
Nope. I tried the 8.4.5 but it appears to have the same problem.
Zoran
