-
Notifications
You must be signed in to change notification settings - Fork 10
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
Bug | Segmentation Fault #88
Comments
Fixed it by using |
Can you try to recreate the segfault while running in gdb? Even if it is fixed for you now, it is always good to learn about possible failure paths. |
@thiesmoeller Of course:
|
Hi! I had this problem aswell and it wasnt solved with the sudo command. However i had a friend help me diagnose it. So the problem lies in gstpylon.cpp:340 as we can see from above. The problem is that when you have nvidia enabled you try to assign stuff to self but if there is an error in the giant catch block before the plugin deletes self and therefore self is null when you try to assign. So my solution was to check the errors above and see if i violated any of them. It turns out since my camera wasnt connected it threw a fault but then the segfault happens before it can report that fault. |
great catch! can you provide a pull request? |
Sadly i have neither the time nor the knowledge of how to do this. I'm but a humble novice conveying what little information i have. |
Describe the issue:
When running tests, or trying to run on a camera, I am getting a segmentation fault:
Reproduce the code example:
Error message:
Is your camera operational in Basler pylon viewer on your platform
Yes
Hardware setup & camera model(s) used
This is happening both on my personal Ubuntu 22.04 computer, and on our Jetson Xavier NX Jetpack 5.1.2.
CPU: X86_64 & ARM64
Operating system: Ubuntu 20.04 & 22.04
RAM: 32Gb & 8Gb
Cable length: 25cm
Deepstream: 6.4
Cuda: 12.3 & 11.4
Runtime information:
The text was updated successfully, but these errors were encountered: