From octave-maintainers-request at bevo dot che dot wisc dot edu Wed Dec 15 14:09:00 1999 Subject: Re: Octave-2.1.14 don't reclaim memory from globals variables that are cleared From: Joao Cardoso To: octave-maintainers at bevo dot che dot wisc dot edu Date: Wed, 15 Dec 1999 20:08:13 +0000 "John W. Eaton" wrote: > On 13-Dec-1999, Joao Cardoso wrote: > > | It seems that the memory used by globals variables at initialization > | can't be reclaimed when the variables are cleared (even with -x): > | > | octave:1> ; used memory: 9492K > | octave:1> a=rand(1000); 17M > | octave:2> clear a; a=rand(1000); 17M > | octave:3> clear a; global b > | octave:4> b=rand(1000); 17M > | octave:5> clear b; b=rand(1000); 25M -- should be 17M > | octave:6> clear b; b=rand(1000); 25M > | > | repeat: (copy/paste) > | > | a=rand(1000); > | clear a; a=rand(1000); > | clear a; global b > | b=rand(1000); > | clear b; b=rand(1000); > | clear b; b=rand(1000); > | > | I'm using octave-2.1.14 on sco-3.2v5.0.4 > > Hmm. I can't seem to reproduce this problem with the current sources > on my Linux system. OK, the last CVS cures the problem; it was still present at octave-2.1.19. One further question: will CVS reflect Octave current (daily or whatever) development status or just the released development snapshots? Thanks, Joao > > > jwe -- Joao Cardoso | e-mail: jcardoso at inescn dot pt INESC, R. Jose Falcao 110 | tel: + 351 2 2094322 4050 Porto, Portugal | fax: + 351 2 2008487