-
Notifications
You must be signed in to change notification settings - Fork 256
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SegFault when using jnius with numpy #490
Comments
Just to note that in numpy/numpy#15691 we tracked it down to be probably related to threading. I.e. setting |
Sorry for lack of answer, it's a bit obscure indeed, and no idea really came to mind.
the fact that it's numpy building from source that fixes is a slight (and wishful) hint to me that the proplem lies on numpy's build, rather than jnius, but i can't really be sure. |
@tshirtman note that if you run on ubuntu, I am not sure that you get openblas by default right now, it might be atlas, or even no blas at all. |
hm, but if i install from the wheel on ubuntu, i do get the segfault. Just not when i build numpy from source, though it's possible that it doesn't build with blas if i don't have it, i didn't get any warning about it though, i'll check. |
You would not get a warning, check EDIT: You may e.g. have a blas intalled, but that may just be a link to atlas |
built from source
from wheel:
|
This ticket is similar to numpy/numpy#15691
As I am not sure where the issue exactly is - jnius or numpy?
Using jnius+numpy causes issues in CentOS7 when python is installed with anaconda.
Reproducing code example:
I can reproduce this exactly with:
Error message:
GDB Traceback for the SegFault:
Numpy/Python version information:
Note: It is reproducible on
It is not reproducible on MacOS.
The text was updated successfully, but these errors were encountered: