Re: trouble with mem sucking slave interps
- From: Jeff Hobbs <jeffh@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 25 Apr 2005 22:26:17 -0700
Matthias Kraft wrote:
I have the situation now were my application creates several slave interpreters (even recursive) and after using deletes them again.
But as it seems deleting a slave does not mean any memory gets freed?! This is an observation with Tcl 8.4.1 on Solaris. I will try to setup something in ActiveTcl 8.4.9 tomorrow.
I looked into this as the application is running for a while and soaked up more and more memory. When the final [exit] in the main interp got called it took several minutes before the shell prompt returned.
Is there anything I can do about it? Maybe before deleting the slave, [unset] on all variables or something?
I'd be curious what you do, and what might be left behind. For the most part, interps clean up after themselves (freeing all commands and vars created). Using 8.4.9 I ran loops of 1000 { interp delete [interp create z] } and saw no mem loss. Note that the creation of each interp creates commands, procs, vars, etc. in initialization.
-- Jeff Hobbs, The Tcl Guy http://www.ActiveState.com/, a division of Sophos .
- References:
- trouble with mem sucking slave interps
- From: Matthias Kraft
- trouble with mem sucking slave interps
- Prev by Date: Re: "list must have an even number of elements"
- Next by Date: Re:
- Previous by thread: Re: trouble with mem sucking slave interps
- Next by thread: one Dll allocates memeory but other do not
- Index(es):
Relevant Pages
|