Open liym27 opened 3 years ago
Can you maybe set the logging level to be verbose and see more info? Also if possible, could you please share the model you are using?
What is your onnxruntime version?
Why jemalloc shows up here?
Please tell us what you changed. The call stack is unusual.
What is your onnxruntime version?
1.5.1
Why jemalloc shows up here?
Can you maybe set the logging level to be verbose and see more info? Also if possible, could you please share the model you are using?
ok
What is your onnxruntime version?
1.5.1
Does the latest onnxruntime release have the same issue?
What is your onnxruntime version?
1.5.1
Does the latest onnxruntime release have the same issue?
Thanks. But I don't use the latest onnxruntime release, and now a new segmentation fault when Ort::Session::Run()
Can you maybe set the logging level to be verbose and see more info? Also if possible, could you please share the model you are using?
What is your onnxruntime version?
1.5.1
Does the latest onnxruntime release have the same issue?
This issue has been automatically marked as stale due to inactivity and will be closed in 7 days if no further activity occurs. If further support is needed, please provide an update and/or more details.
Describe the bug
Run code:
Segmentation fault c++ stack
Urgency If there are particular important use cases blocked by this or strict project-related timelines, please share more information and dates. If there are no hard deadlines, please specify none.
System information
To Reproduce
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Additional context Add any other context about the problem here. If the issue is about a particular model, please share the model details as well to facilitate debugging.