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

[Mike Miller]

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

I just thought of something very easy you can try that might shed some light
on whether the segfault you are seeing on Windows is the same that I am
seeing.

Try setting the OMP_NUM_THREADS environment variable to 1 before any image
functions are called. If you're running from a msys shell or other unixy-type
shell, you could export OMP_NUM_THREADS=1 from there before calling octave. If
not, set it in the Octave shell before your scripts or any image-related
functions are called:


setenv OMP_NUM_THREADS 1;


This prevents OpenMP from spawning additional threads in the background, and,
at least for the condition I see, prevents the segfault from occurring at
exit.

    _______________________________________________________

Reply to this item at:

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

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