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

[Hartmut]

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

I've done some more testing concerning the "test imread" connected segfaults
under Windows.

To start with my personal highlight: Even with the 4.0.1 release (official
Windows installer) I get a difference between using octave.exe and
octave-gui.exe!

Here are the full details:

All tests are done under Windows 7. All compilation was done under Ubuntu
14.04.

I used two different tests:
* test "A" means "test imread, clear all, test imread"
* test "B" means "test imread, exit"

I have tried three different ways to start Octave:
* using bin/octave.exe
* using bin/octave-gui.exe
* using bin/octave-cli.exe

I have used five different Windows binaries (newest first):
* "JWEstatic": own mxe-octave build, default branch up to cset ecce63c99c3f,
including JWE's patch "avoid multiple definitions of static function-scope
vars"
* "OpenMP": own mxe-octave build, default branch up to cset 6619945e4434,
including the "OpenMP patch"
* "Rikshack": own mxe-octave build, default branch, including Rik's "hack"
from comment #12 (that never made it to the repository)
* "4.0.1": official 4.0.1 release Windows binaries
* "4.0.0": official 4.0.0 release Windows binaries

My results are:

"JWEstatic" binaries:
* octave.exe    : A = OK, B = OK
* octave-gui.exe: A = OK, B = OK
* octave-cli.exe: A = OK, B = OK

"OpenMP" binaries:
* octave.exe    : A = OK, B = crash
* octave-gui.exe: A = OK, B = crash
* octave-cli.exe: A = OK, B = OK

"Rikshack" binaries:
* octave.exe    : A = OK, B = OK
* octave-gui.exe: A = OK, B = OK
* octave-cli.exe: A = OK, B = OK

"4.0.1" binaries:
* octave.exe    : A = OK, B = segfault
* octave-gui.exe: A = crash, B = segfault
* octave-cli.exe: A = OK, B = OK

"4.0.0" binaries:
* octave.exe    : A = OK, B = segfault
* octave-gui.exe: A = OK, B = segfault
* octave-cli.exe: A = OK, B = OK

Here are some subjective observations on those results:
* The CLI version never has any problems with this kind of "test imread"
segfaults
* There are many Octave versions, where starting "bin/octave.exe" results in a
different segfault behavior compared to "bin/octave-gui.exe". This is even
true for official Windows release binaries.
* The segfault behavior of "bin/octave-gui.exe" changed from the official
4.0.0 release to the official 4.0.1 release.
* The segfault behavior is different between my Windows PC and Avinoams
Windows PC. This difference might either be due to a different Windows
environment, or due to a different Linux environment for compilation.

@Avinoam: In order to validate the last point. I would be willing to run your
latest Windows executables on my Windows PC if you find a way to make the zip
file accessible to me. (I will be two days offline from now on, though...)

I hope that anyone with more understanding can use those results to further
hunt down the origin of this bug.


    _______________________________________________________

Reply to this item at:

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

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