Octave gobbles up and will not release memory allocated in functions
after access in a for loop
Kernel:
Ubuntu 7.10 2.6.22-14-generic #1 SMP Sun Oct 14 21:45:15 GMT 2007
x86_64 GNU/Linux
Octave(From Ubuntu Repositories):
GNU Octave, version 2.1.73 (x86_64-pc-linux-gnu).
Steps to reproduce(CAUTION may hang due to swappiness):
$ octave < dud.m
And watch the memory burn away.
"clear" helps, but not completely. And no, doing away with the for
loops is not possible. This is a simplified example of a much more
complex function.
Remove the line inside the nested for loops to see the memory usages difference.
I'd like to know of any octave command or setting that forces garbage
collection on the system to prevent this.