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

[Mike Miller]

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

When I was working on bug #41699, one of my theories was that GraphicsMagicks
builds itself with OpenMP, and when the shared library was released it left an
OpenMP thread pool running. Building Octave with -fopenmp (which we do by
default now) solved that for me on Debian but didn't solve the crash on
Windows, though.

The idea that GraphicsMagick has some kind of resource that isn't released
properly when the shared library is unloaded seems plausible to me, whether
it's OpenMP threads or static variables or some other resource.

    _______________________________________________________

Reply to this item at:

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

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