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

[Rik]

Follow-up Comment #90, bug #47372 (project octave):

I can confirm that the classdef leaks are now gone.  The only ones I see are
now from putenv (which I don't believe can/need to be fixed).

One question, I have a small m-file tst_leak.m that contains


__run_test_suite__
exit


I have been testing by executing this statement from the command line


./run-octave -f tst_leak.m |& tee leak.log


When I do this I find only 3073 bytes are leaked.  However your test log shows
32569 bytes leaked.

How are you running the test suite?  Are you directly starting Octave and
entering commands?


./run-octave -f --no-gui
__run_test_suite__
exit


I wasn't overly concerned about the remaining leaks in various parts of the Qt
libs because they don't seem to grow with time, and they might just be there
because we don't free the resources and instead let the operating system reap
the process and all of its memory.  But we could try to locate them. 
Shouldn't we be calling QCoreApplication::quit() somewhere?



    _______________________________________________________

Reply to this item at:

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

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