[Octave-bug-tracker] [bug #55287] Memory leak in graphics subsystem

[Rik]

Follow-up Comment #21, bug #55287 (project octave):

I think you are right that there is nothing to be done about libfontconfig. 
The library itself seems to have a leak, and there is no real way to get rid
of it.  I configured using '--without-fontconfig' and I STILL got a leak in
the library.  At least it is stable at about 4KB and never changes.

As for the lost memory during initialization of the interpreter.  This seems
to be intended (jwe changeset).  The code that leaks is


    // Yes, this object is intentionally not deleted in the destructor
    // so that we avoid a crash on exit for user-defined data types.
    // See bug #53156.  If that problem is properly fixed, then this
    // could be stored as an object instead of a pointer to an object
    // allocated with new.

    vals(i) = new octave_value (val);


So, are we done?  No more memory leaks to find?


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?55287>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/