[Octave-bug-tracker] [bug #31644] Memory leaks

[John W. Eaton]

Follow-up Comment #3, bug #31644 (project octave):

Do these messages only appear when you exit?  Is this happening because
Octave is not explicitly freeing some memory before it exits?

If there is a leak in parsing and evaluating this function, then I would
expect

  while (1) try fun; end; clear fun; end;

to cause Octave's memory usage to constantly grow, but I don't see that when
I watch the process with top.  I would also expect valgrind to tell me that
more memory is lost the longer I run the loop, but that doesn't seem to be
happening either.

I'm not sure these leaks are something we need to worry about, but if you can
find something that leaks when run in a loop and that makes the Octave process
measurably grow and not just generate messages from valgrind when Octave
exits, then I'll try to take a look at it.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?31644>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/