Well, this doesn't appear to explain my memory problems:
# LD_LIBRARY_PATH=`pwd` ./tclsh
% info patchlevel
8.4.6
% lappend auto_path /usr/local/src/thread/unix; package require Thread
2.6.1
% exec ps -p [pid] -o pid,vsz,rss,args
PID VSZ RSS COMMAND
23736 5176 1824 ./tclsh
% for {set i 0} {$i < 1000} {incr i} {
thread::join [thread::create -joinable {}]
}
% exec ps -p [pid] -o pid,vsz,rss,args
PID VSZ RSS COMMAND
23736 5420 2052 ./tclsh
%
But this does support your conclusion that 8.4.6 is ok. I guess it's a
good thing I never took the time to upgrade! :)
I will get back to running valgrind and trying to figure out what's
going on eventually; right now I'm busy unpacking and working on a
client project but I should have more time soon.
janine
On Apr 6, 2005, at 8:11 PM, Dossy Shiobara wrote:
On 2005.04.06, Janine Sisk <[EMAIL PROTECTED]> wrote:
The system I'm having the most leak problems on is already using
8.4.6,
unfortunately. But I'd like to try your test code anyway and see what
happens. Where do I get this Threads extension?
http://cvs.sourceforge.net/viewcvs.py/tcl/thread/
$ cvs co -d :pserver:[EMAIL PROTECTED]:/cvsroot/tcl co thread
-- Dossy
--
Dossy Shiobara mail: [EMAIL PROTECTED]
Panoptic Computer Network web: http://www.panoptic.com/
"He realized the fastest way to change is to laugh at your own
folly -- then you can let go and quickly move on." (p. 70)
--
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.
--
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.
