-
-
Notifications
You must be signed in to change notification settings - Fork 357
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 on re-init pipeline #182
Comments
Did you change something in nvdsinfer_custom_impl_Yolo files? Which is your Ubuntu, CUDA, TensorRT and DeepStream versions? Which model are you using? |
Nothing was changed.
|
It looks like lots of other issues are also present regarding argus daemon and such .. In my case, I create a process, create/clean multiple pipelines in parallel (thread per pipeline) without ever killing the process to start over .. Having ancient kernel and gstreamer versions at nvidia's side doesn't help either .. |
I use a dynamic pipeline for my commercial projects without any issue. But I keep the pipeline running and change the input and output elements (adding or removing them). |
Hey, I am facing the exact same issue. Was there any fix for this? When I switch to the https://github.com/NVIDIA-AI-IOT/yolov4_deepstream, it seems to work without any issues. My Setup is: Ubuntu 20.04 Thanks. |
Can you check the RAM memory usage when your code is running? If possible, run with gdb to debug the segmentation fault. |
Hey, I ran with gdb and it segfaults with this error
Are there any specific gdb flags you want me to try? Thanks. |
@marmikshah I met the same problem. did you solve it? CUDA: 11.7 @marcoslucianops this is my log: |
@thunder95 I have not been able to find a solution to it. So temporarily I have reverted to using DetectNet instead of Yolo. |
Try to use the new ONNX implementation. |
hi, Has this problem been solved? |
Hi,
I've made a few functions in C which constructs a pipeline using nvinfer and this yolo lib.
When:
Following crash happens 100%
Disassembly:
The text was updated successfully, but these errors were encountered: