[Octave-bug-tracker] [bug #41699] imformats causes a segmentation fault on Windows when Octave exits

[Amro]

Follow-up Comment #91, bug #41699 (project octave):

Let me point out another interesting thing: unlike octave.exe, octave-cli.exe
does not crash on exit. As I understand, the CLI version is not compiled with
Qt at all, perhaps this has something to do with it...

Here is a simple test to trigger the segfault:


# octave.exe
C:> octave --no-gui --no-window-system --eval "imread('somefile.png');
disp('bye');"
warning: your version of GraphicsMagick limits images to 8 bits per pixel
warning: called from
    imformats>default_formats at line 256 column 11
    imformats at line 79 column 3
    imageIO at line 106 column 11
    imread at line 106 column 30
bye
panic: Segmentation violation -- stopping myself...
attempting to save variables to 'octave-workspace'...
save to 'octave-workspace' complete
 
# octave-cli.exe
C:> octave-cli --no-gui --no-window-system --eval "imread('somefile.png');
disp('bye');"
warning: your version of GraphicsMagick limits images to 8 bits per pixel
warning: called from
    imformats>default_formats at line 256 column 11
    imformats at line 79 column 3
    imageIO at line 106 column 11
    imread at line 106 column 30
bye


The above was tested in Octave 4.0.0 (the official Windows build).


    _______________________________________________________

Reply to this item at:

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

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