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

[Hartmut]

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

Bad news here. Please reopen this bug report.

I have just tested the official Windows installer of the Octave 4.0.2 release
under Windows 7. (It should have all the relevant patches in.)

My observations are:

* When I run "test imread, exit", then I never get any segfault. So far, so
good.

* When I run "test imread, clear all, test imread", then it  depends on how I
start the Octave GUI. The following ways to start Octave DO CRASH on the above
commands! 
** use the Desktop shortcut "Octave-4.0.2 (GUI)"
** use the created shortcut in the Windows Start Menu
** use /bin/octave-gui.exe

* When I start Octave in the following different ways,then the commands "test
imread, clear all, test imread" DO NOT CRASH.
** use bin/octave-4.0.2.exe
** use bin/octave.exe
** use bin/octave-cli.exe

So there seems still to be something going on, which is special to Windows.

If this cannot be easily fixed, than my suggestion would be, that we keep
"normal users" away from this crash, by replacing the currently used command
"octave-gui.exe" by the well behaved command "octave.exe" in the startup file
"octave.vbs". This would take care of the Desktop link (and also the start
menu entry?)

    _______________________________________________________

Reply to this item at:

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

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