[Octave-bug-tracker] [bug #41699] imread causes a segmentation fault when exiting Octave

[Mike Miller]

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

Even though we have proven (I think?) that this is not related to
GraphicsMagick's use of OpenMP (see bug #42176), this still looks to me to be
related to unloading the __magick_read__.oct file, which in turn unloads and
runs destructors in the GraphicsMagick library because it is only linked to
that one oct-file. And this seems to be doing something that crashes Octave on
Windows.

Note that "clear all" clears functions from the symbol table. You should also
be able to reproduce this crash with any of the following after "test
imread":


clear -f
clear functions
clear __magick_read__


I can get the same crash on Linux but only because of OpenMP. By defining
OMP_NUM_THREADS=1, or building Octave with --enable-openmp, the crash does not
happen on Linux.

Earlier in this report we saw that defining OMP_NUM_THREADS=1 has no effect
and still crashes Octave on Windows.

    _______________________________________________________

Reply to this item at:

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

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