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

[John W. Eaton]

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

I traced (at least some of) the classdef leaks to the way classdef functions
are handled.

The parser generates a classdef object that contains pointers to all the
functions (all dynamically allocated memory for the parse tree nodes).  The
classdef object is stored in parser.classdef_object.  Then that is used in the
parse_fcn_file function to create the meta class for the classdef object, and
a pointer to the classdef constructor function is returned.

I think all of the functions end up in the symbol table, but the
classdef_object field of the octave_base_parser object never seems to be
deleted anywhere that I can see.


    _______________________________________________________

Reply to this item at:

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

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