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

[Hartmut]

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

I have tested the patch from comment #12 under Windows, and 
* it works wonderfully to eliminate the long standing crashing that seem to
come from memory leaks. 
* But unfortunately this patch also revives another (already closed) bug that
also creates crashes.

Here are the details:

I added the mentioned small patch as
"stable-octave-1-testimagesegfaults.patch" to the src folder of the MXE Octave
source directory. Then I compiled MXE Octave with the current tip of the
Octave stable branch:

autoconf
./configure
make zip-dist


I unpacked the zip file on a Windows 7 machine and started
bin/octave-gui.exe.

Here are the results of my tests:
A) When I run this

test imread
clear all
test imread

Then
* with Octave-4.0.1-rc4: I get an immediate crash of the Octave GUI
* with the patched version: no crash

B) When I run this

test imread
exit

Then
* with Octave-4.0.1-rc4: I get a segfault on exit
* with the patched version: no segfault

C) I run several image processing scripts. I could NOT produce any segfaults
on exit.

D) While running my personal set of image processing scripts, I sadly
discovered that bug #45372 came back to life with this patch!
Here is an example of how to produce the crash of this (already closed) bug
report:

I = uint8(100.*ones(20,20,3));
imshow(I)
% now click with the left mouse button into the figure window

Observation:
* with Octave-4.0.1-rc4: no problem (bug has already been fixed)
* with the patched version: immediate crash of the GUI when clicking

My personal conclusion regarding this patch: I consider the "crash on click"
bug even more severe, compared to the two (memory leak induced) bugs "clear
all provokes crashes" and "segfault on exit". So unless the revived bug #45372
can be easily wiped out for this patch, I would (very sadly) NOT vote to
include this patch into a new Octave-4.0.1-rc5 release candidate.

    _______________________________________________________

Reply to this item at:

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

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