-
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 Faults Because of Small RAM Size??? #3341
Comments
From my experience, boards like this often come without configured swap file. Perhaps this is a better option? |
Hi @dorodnic I already have 2GB of swap file size. Should I increase this? Or is there an alternative solution? |
It should be plenty. Are you sure the issue is related to out-of-memory situation? What data are you seeing using htop? |
Are you getting stable memory when running |
Hi @dorodnic Yes, memory hovers around 290 MB when running rs-capture. Would reverting NumPy to a previous version affect my code? |
I think it should be fine. I'm just suggesting one possible source for the problem. Perhaps the application is doing some additional heavy processing, maybe storing multiple frames? |
@ShadowHunter0510 Any update for Dorodnic's question? Thanks! |
@dorodnic I'm also getting segfaults for, i.e. My specs:
In my case, I'm also getting
|
@jdwolk Did you try if you still get segmentation fault with rs-depth if change to lower resolution or FPS? Such as 480x270@30fps or 640x480@15fps |
@jdwolk Any update? Thanks! |
We ended up moving to Raspberry Pi which opened up separate issues (see IntelRealSense/realsense-ros#652, IntelRealSense/realsense-ros#669 ). I can try again in a few days with the Beaglebone. |
@jdwolk Any update? Thanks! |
@jdwolk Do you still need support on this issue? Please update. Thanks! |
I am having similar behaviour with the Raspberry Pi. Getting segmentation fault using the realsense-viewer or python scripts using pyrealsense2. |
@filipematosinov Did you try rs-depth to see if it works or not? |
@filipematosinov @jdwolk @ShadowHunter0510 Any other questions for this ticket? Please update. Thanks! |
I have tried rs-depth having the same issue |
@filipematosinov What's the resolution and FPS configuration when you get issue for rs-depth? |
@filipematosinov Looking forward to your reply? Could you please update? Thanks! |
@filipematosinov If no other questions, will close the ticket at this point. Thanks! |
Issue Description
It appears that a few other users and I have been encountering segmentation faults on the Raspberry Pi. I believe that this may be because there is not enough dedicated RAM size. My program relies on an infinite loop, which would of course increase the chances of segmentation faults, since it tracks distance in real time. Perhaps is there any way to “clear” the data that would be obtained from each frame captured when the program loops again? The program may be storing this data that is only necessary for relaying the distance for one instance at a time.
The text was updated successfully, but these errors were encountered: