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

[John W. Eaton]

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

Rik:

Yes, I looked at the classdef leak.  I see where it is coming from.  The
classdef object created in the parser is never cleaned up, but I'm not sure
yet where or when that should happen.

I don't see a crash with "test imread".

I'm building on an x86_64 Debian testing system.  I used


.../configure --disable-java --enable-address-sanitizer-flags --disable-jit
--without-opengl --disable-docs --prefix=/usr/local/octave/dev-asan
--with-hdf5-includedir=/usr/include/hdf5/serial
--with-hdf5-libdir=/usr/lib/x86_64-linux-gnu/hdf5/serial CFLAGS="-O0 -ggdb3"
CXXFLAGS="-O0 -ggdb3" FFLAGS="-O0 -ggdb3"


I'm running a full make check now to see if I have any crashes with this
configuration.  When I ran the tests in batches, I did see leaks for anything
that used classdef, but I didnt't see any crashes.

I do see that my copy of Octave built with these options won't start the GUI. 
It just exits without any message.  So all my tests have been done with
"octave --no-gui"

There are some Qt and fontconfig leaks as well.  I'm guessing those are
happening because we aren't really deleting things when shutting down the GUI.
 It would be nice to fix those as well, but I'm not too concerned about them
at the moment.

    _______________________________________________________

Reply to this item at:

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

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