-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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 importing tensorflow before ortools #3230
Comments
It usually means that tf is linked with an older version of protobuf. What happens if you import tf after or-tools ? There is nothing we can do about it. |
related to: |
Tensorflow uses protobuf even older than what ortools v9.2 uses, but ortools v9.2 works fine. Was there any change in a way of linking protobuf in v9.3? |
@Mizux This is slightly different from: because importing packages actually succeeded but segmentation fault happened during
|
@Mizux Is there any plan to fix this in next release? |
For next release v9.4 no, I want to release it ASAP. |
Yes, we bumped to 3.9.14.
Nothing in our code has changed
Le ven. 8 avr. 2022, 18:15, Youchang Kim ***@***.***> a
écrit :
… Tensorflow uses protobuf even older than what ortools v9.2 uses, but
ortools v9.2 works fine. Was there any change in a way of linking protobuf
in v9.3?
—
Reply to this email directly, view it on GitHub
<#3230 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACUPL3NM2O4YZBCB7NHRS3LVEBLTDANCNFSM5S2IEV3A>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
Works fine now. |
What version of OR-Tools and what language are you using?
Version: v9.3
Language: Python
Which solver are you using (e.g. CP-SAT, Routing Solver, GLOP, BOP, Gurobi)
CP-SAT
What operating system (Linux, Windows, ...) and version?
macOS BigSur x86-64
What did you do?
import tensorflow
beforefrom ortools.sat.python import cp_model
What did you expect to see
What did you see instead?
Anything else we should know about your project / environment
The text was updated successfully, but these errors were encountered: