Segmentation Fault on ONNX 1.1.2
See original GitHub issueI am using onnx 1.1.2 and Caffe2, and when I do the following, I get a segmentation fault:
from caffe2.python import core
import onnx
Swapping the order of the above imports doesn’t change the error. backtrace: https://gist.github.com/pooyadavoodi/53c6d0ce381f9a41e8fbd79bb555176c
I built onnx from branch rel-1.1.2 and it works. So the problem is only the pip package I think.
Issue Analytics
- State:
- Created 5 years ago
- Comments:23 (16 by maintainers)
Top Results From Across the Web
imx8 plus onnx segmentation fault with NPU - NXP Community
Hi I am succeed execute onnx model run on imx8 plus cpu, but same code with OrtSessionOptionsAppendExecutionProvider_VsiNpu causing a ...
Read more >Segmentation fault (core dumped): It crashes when compiling ...
TVM throws Segmentation fault (core dumped) at relay.build() when compile a ONNX model in CUDA. Please notice that: the script run well when ......
Read more >onnxruntime segfault | The AI Search Engine You Control
I get a segfault with running inference on the logistic regression model generated with sklearn-onnx. System information. OS Platform and Distribution: ...
Read more >Unable to import onnx model using tidlModelImport ... - TI E2E
I converted a pytorch model (.pth) to onnx (.onnx) format in order to use it. However the import utility fails with a segmentation...
Read more >onnx2tf - PyPI
Self-Created Tools to convert ONNX files (NCHW) to ... of this tool is to solve the massive Transpose extrapolation problem in onnx-tensorflow (onnx-tf)....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

This is not related to pytorch or caffe2 but the combination of an upstream issue in pybind11 https://github.com/pybind/pybind11/issues/1262 and the way onnx binary packages were built. We don’t have a way to fix a released version (pypi doesn’t allow resubmit another packages for a released version). Installing onnx via
pip install --no-binary onnx onnxwould force pip to use source package to fix this issue, and @raymondxyang is going to help us on updating the release pipeline (see discussions here https://github.com/onnx/onnx/pull/1183) so for future release this issue should go away.Newly published 1.3.0 was built with a newer gcc and has been out on pypi. I tested it with pytorch and seems the problem is gone. If there is any problem please report.