-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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 Running distance_to_object.ipynb #3282
Comments
@ShadowHunter0510 What's the FW and librealsense version you're testing? |
The librealsense version that I’m using is 2.17.0, and the firmware version is 05.10.13.00. |
@ShadowHunter0510 Did you see this problem on PCs? Or you just got this issue on Raspberry Pi? |
I’ve only been using a Raspberry Pi, so I’ve only been encountering these issues on that motherboard. |
@ShadowHunter0510 Could you please have a try on PC first? I tired on my PC and didn't get the issue. I'll try to set up a Raspberry Pi to see if any issue there. |
I think it might be something to do with the Raspberry Pi. In Issue #3303, another user confirmed that it could be causing all the problems? Can you tell me the results that you get? |
@ShadowHunter0510 Might be related to memory leak with python as mentioned in #3341 |
@ShadowHunter0510 I saw you have another ticket #3180 is also reporting "Segmentation Fault". Seems duplicate? And I'm sorry I didn't find Raspberry Pi for the set up yet. You can keep an eye on #3180 and #3341 at first. Thanks! |
@ShadowHunter0510 As this is duplicate with #3180 Let's track there and close this accordingly. Thanks! |
Issue Description
When running sample Python code such as distance_to_object.ipynb, I get an error that simply says “Segmentation Fault” about half of the time that I run the program. Oftentimes it fixes itself when I rerun the program, but other times it requires for me to manually unplug the camera and replug it again to get rid of the problem. It either happens right before it says “Frames Captured” in the code, or if I am running the code in a loop, it would happen at the end of the current cycle in the loop.
The text was updated successfully, but these errors were encountered: