[Numpy-discussion] Numpy intermittent seg fault

[Nathaniel Smith]

On Thu, Dec 10, 2015 at 4:05 PM, Jacopo Sabbatini
<jacopo.sabbatini at roames.com.au> wrote:
> Hi,
>
> I'm experiencing random segmentation faults from numpy. I have generated a
> core dumped and extracted a stack trace, the following:
>
> #0  0x00007f3a8d921d5d in getenv () from /lib64/libc.so.6
> #1  0x00007f3a843bde21 in blas_set_parameter () from
> /opt/apps/sidescananalysis-9.7.1-42-gdd3e068+dev/lib/python2.7/site-packages/numpy/core/../../../../libopenblas.so.0
> #2  0x00007f3a843bcd91 in blas_memory_alloc () from
> /opt/apps/sidescananalysis-9.7.1-42-gdd3e068+dev/lib/python2.7/site-packages/numpy/core/../../../../libopenblas.so.0
> #3  0x00007f3a843bd4e5 in blas_thread_server () from
> /opt/apps/sidescananalysis-9.7.1-42-gdd3e068+dev/lib/python2.7/site-packages/numpy/core/../../../../libopenblas.so.0
> #4  0x00007f3a8e09ff18 in start_thread () from /lib64/libpthread.so.0
> #5  0x00007f3a8d9ceb2d in clone () from /lib64/libc.so.6

Given the backtrace this is almost certainly some sort of bug in
openblas, and I'd suggest filing a bug with them.

It's possible that we might have accidentally added a workaround in
1.10.2 (release candidate currently available, final should be out
soon). There was some environment variable handling code in numpy 1.9
through 1.10.1 that triggered problems in some buggy libraries (see
numpy issues #6460 and 6622); possibly the workaround for those issues
will also workaround this issue. But if not then I'm not sure what
else we can do, and it's probably a good idea to file a bug with
openblas regardless.

-n

-- 
Nathaniel J. Smith -- http://vorpus.org