-
Notifications
You must be signed in to change notification settings - Fork 64
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
Segmentation fault when juliacall
is imported before torch
#435
Comments
Attached are other information which might be relevant to reproduce the bug: gdb trace and the list of installed packages (in plaintext and as environment.yml renamed environment.yml.txt to pass github filetype filter). |
It looks like this problem was mentioned in pytorch.#78829: while the issue 78829 is about the order "import torch; import juliacall", the comment cited above says
which is consistent with this issue. Three more observations:
|
You appear to be using There are a number of possibilities here. You could for example configure Julia to use MKL. |
Minimal example:
The segfault happens at 0x00007fffa673c342 in __kmp_env_blk_init () in libgomp.so.1
Importing only one of the two modules does not result in an error.
Note that this issue is related but different from #215: here
juliacall
is imported beforetorch
, and theretorch
is imported beforejuliacall
.Environment details:
1.11.0.post202
(pytorch-gpu, build cuda112py310h68407e5_202)Similar issues:
torch
is imported beforejuliacall
, but not the reverse FAQThe text was updated successfully, but these errors were encountered: