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

[John W. Eaton]

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

I checked in the following changeset for the program name problem.

http://hg.savannah.gnu.org/hgweb/octave/rev/eff26982a19b

After making this change, I was able to build with OpenGL enabled (but I left
docs and java disabled) and run "make check".  No obviously new leaks due to
OpenGL showed up for me when doing that.

I'm still unable to start the GUI with the address sanitizer.

I tried running "./run-octave --no-gui" and doing "demo colorbar" and then
exiting.  I saw


SUMMARY: AddressSanitizer: 31450 byte(s) leaked in 712 allocation(s).


but nothing else.  I'm using the qt toolkit.

Then I tried running "./run-octave --no-gui" and doing "rundemos" to run all
the demos (we have a large collection now!) and was able to step through all
of them with no crashes or major issues.  The summary was:


SUMMARY: AddressSanitizer: 89375 byte(s) leaked in 1580 allocation(s).


I'm attaching the full leak log for this test.

In all of that, there is one one case that points directly back to Octave (72
bytes lost in three allocations from the ListDialog object).

Given all that Octave does for those demos, I'd say that's a remarkable
result!

(file #36910)
    _______________________________________________________

Additional Item Attachment:

File name: leak-log-for-demos-with-opengl.txt Size:17 KB


    _______________________________________________________

Reply to this item at:

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

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