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

[Rik]

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

This bug report is now very long.  The memory leaks portion has mostly been
dealt with.  Do we want to keep it open for the segmentation faults with
imread on Windows platforms, or should the discussion move back to the
original bug report?

Also, the command


./run-octave -f


returns immediately to the prompt for me.  There doesn't appear to be any
segfault, but I can't run a binary built with the AddressSanitizer to check if
there are leaks in the GUI.  Should I file a separate report for that or
continue here?


    _______________________________________________________

Reply to this item at:

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

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