-
Notifications
You must be signed in to change notification settings - Fork 196
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
examples/stereo_depth_video.py segfault #520
Comments
I am getting this same error on one of my production boxes using OAK-D-POE using standard center RGB camera. For whatever reason that one box throws it after ~10-90 minutes of running continuously. However, another box I upgraded using the same hardware (PC & cameras) has been running solid for 3 days on the 2.15.0 release. Stack trace (most recent call last): |
Sorry for the issues at hand @Petrox @chris-piekarski @Petrox how long after the segfault arrises on the example you've ran? Is it immediate or happens after some time of running? @chris-piekarski Were both boxes running version 2.15.0? If that is the case, do you happen to know any other differences that might be at play here. In any case, we are still on the hunt to track down some additional stability issues, which I think could be pertinent here in both cases. We'll keep you updated |
Yes both boxes running 2.15.0 @themarpe |
We'll take a further look into this and get back |
Computer: corei7-7700hq with lots of ram and IO, no resource starving.
The disparity image was low quality, displayed "ghosts" (non existent close objects which were visible when I moved the camera (oak-d-lite), then suddenly segfault. (which is not an acceptable way to handle any issues)
The text was updated successfully, but these errors were encountered: