[Octave-bug-tracker] [bug #47372] Memory leaks and segmentation faults in Octave

[Rik]

Update of bug #47372 (project octave):

                 Summary: memory leaks in octave-link, octave-qt-link,
octave-mutex => Memory leaks and segmentation faults in Octave

    _______________________________________________________

Follow-up Comment #5:

I built Octave as described in the original bug report.  I then tried to
search for other memory leaks in Octave by running


./run-octave -f --no-gui --eval '__run_test_suite__; exit'


This does make it through the test suite, but then segfaults on exit without
producing a report on the leaks.

I changed tactics and started octave as before, but then ran 'runtests
scripts/XXX' followed by exit.  Most directories showed no leaks, but the
following had problems.


general/  : Extra leaks
image/    : Segfault on exit
java/     : Extra leaks
miscellaneous/ : Small extra leak
optimization/ : Extra leaks
plot/util : Segfault on exit
prefs     : Small extra leak (probably due to setenv)


I think this tool may help us get to the bottom of some longstanding strange
behavior we have seen.  For example, running a java command is enough to
change the output of svds.  That could be explained by the massive memory
leaks that are happening when the JVM is used.  Similarly, on Windows there
has been a longstanding bug that whenever imformats was used, Octave would
segfault on exit.  I think that probably explains the segfault in the image/
directory.


    _______________________________________________________

Reply to this item at:

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

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