-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
[MacOS] Segmentation Fault w/ Torch #4897
Comments
Thanks for the excellent write-up and example code! I'll try running this example on my Mac tonight to see if I can reproduce the issue. |
@Innixma Hey, thanks for writing this issue! This is the same issue as dmlc/xgboost#7518. Please try any of the following workarounds:
|
It is indeed fixed when I downgrade libomp, I was using 12.0.1 and segfault goes away when I use 11.1.0 via:
Thanks for the help! Feel free to close this issue if it is a duplicate. |
This issue has been automatically locked since there has not been any recent activity since it was closed. To start a new related discussion, open a new issue at https://github.com/microsoft/LightGBM/issues including a reference to this. |
Description
MacOS segmentation faults if torch is imported before LightGBM and LightGBM trains:
Reproducible example
First create python venv, then:
Example output:
Environment info
LightGBM version: 3.3.1, but I've tested on various different versions of LightGBM and Torch, none worked.
OS Details:
libomp version: 12.0.1 (13.0.0 also fails)
Additional Comments
This bug is problematic in AutoGluon because depending on the order models train, if a torch model trains before LightGBM, LightGBM will cause a segmentation fault. On my old Mac I didn't get this issue likely because my OS was older. This might be specific to Big Sur, but it's unclear. Linux works fine, haven't tried Windows.
The text was updated successfully, but these errors were encountered: