On 2005.04.06, Dossy Shiobara <[EMAIL PROTECTED]> wrote:
> OK, time to binary search to figure out what Tcl version introduced this
> leak.  :-)

OK, looks like Tcl 8.4.7 introduced the leak.  Here's my test run
against Tcl 8.4.6:

    $ LD_LIBRARY_PATH=`pwd` ./tclsh
    % info patchlevel
    8.4.6
    % lappend auto_path /usr/lib/tcl8.4; package require Thread
    2.6.1
    % exec ps -p [pid] -o pid,vsz,rss,args
      PID   VSZ  RSS COMMAND
     8317 12704 1996 ./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
     8317 21192 2272 ./tclsh

Same test against Tcl 8.4.7:

    $ LD_LIBRARY_PATH=`pwd` ./tclsh
    % info patchlevel
    8.4.7
    % lappend auto_path /usr/lib/tcl8.4; package require Thread
    2.6.1
    % exec ps -p [pid] -o pid,vsz,rss,args
      PID   VSZ  RSS COMMAND
     9358 12692 2000 ./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
     9358 48272 29432 ./tclsh


If anyone wants to review the changes to Tcl between 8.4.6 and 8.4.7,
you can produce the diff like this:

    $ cvs -z6 -d :pserver:[EMAIL PROTECTED]:/cvsroot/tcl rdiff -rcore-8-4-6 
-rcore-8-4-7 tcl > tcl-846-847.diff

In the meantime, everyone who is seeing unexplained nsd memory growth if
you're running Tcl >= 8.4.7, please roll back to Tcl 8.4.6 and see if
that makes the problem go away.  (Andrew?  Janine?  etc.)

-- 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.

Reply via email to