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

[Rik]

Update of bug #55287 (project octave):

                 Release:                   5.0.0 => 5.0.1                  

    _______________________________________________________

Follow-up Comment #51:

@Pantxo: Seems like your text in comment #49 got clipped.

I do agree that ASAN isn't very helpful here since the memory is freed on exit
from Octave.  We need intermediate memory reporting, for which I have been
using top, but any tool, including the patch attached to this report, should
work for that.  'top' is easier for me because it is built-in to the OS, and
as I go backwards as far as 3 years ago in the code base it becomes hard to
compile add-ins like the memory tool.

I think there are at least two bugs here which is why we are getting different
behavior when the action is plot() versus set().  Rather than decide on the
definitive test, I would just choose which test you want to debug first and
mention it when you present results.


    _______________________________________________________

Reply to this item at:

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

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