-
Notifications
You must be signed in to change notification settings - Fork 101
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 during julia.Julia() if PyTorch is already imported #125
Comments
And here's the top of the GDB traceback.
|
Update: this doesn't happen on a slightly older PyTorch binary (0.2.0_2). Maybe the change mentioned here as fixing a different dylib incompatibility broke something with libjulia? |
Probably JuliaLang/julia#19606 |
It's been fixed in PyTorch version 0.3 (out this week), I think by reducing TLS usage; regardless it's definitely not pyjulia's fault so I think I'll close |
Nice! |
Similar issue when I import torch in Julia using PyCall. Import again, and get follow errors. signal (11): Segmentation fault |
I'm still seeing this issue on macOS. Any tips for debugging @jekbradbury? Here is the PyTorch thread with more info: pytorch/pytorch#78829 |
The Python package PyTorch occasionally has import order issues with other large binary packages (throwing the static TLS error shown below for one import order but working with the other), but this time one order causes a segfault in
julia.Julia()
, preventing me from using both packages in the same program.Otherwise pyjulia and PyCall work fine for me.
Other possibly relevant versions:
PyCall: v1.15.0
pyjulia: master
The text was updated successfully, but these errors were encountered: