Closed ekolve closed 2 years ago
Really weird! I'll have a look at this soon. Thanks for making the issue.
Perhaps related to #159? I've had segmentation faults occur when the C SDK is passed the compressed/MJPEG color image rather than the decoded BGRA32 image it requires.
I wanted to update this issue in case anyone ever runs in to this. We discovered that the USB-> barrel connector cable (power) to the Azure Kinect was plugged in to a 1A/5V USB port. The docs state that the Azure Kinect can consume up to 5.9 watts. When we plugged the cable into an AC USB adapter that can output 2.2 amps, we stopped getting segfaults.
I wanted to update this issue in case anyone ever runs in to this. We discovered that the USB-> barrel connector cable (power) to the Azure Kinect was plugged in to a 1A/5V USB port. The docs state that the Azure Kinect can consume up to 5.9 watts. When we plugged the cable into an AC USB adapter that can output 2.2 amps, we stopped getting segfaults.
In case anyone needs a reference to the "5.9 watts", here it is.
When I run the following snippet, a segfault is triggered and the machine the Azure Kinect is connected to crashes (shutdown).
Error:
What is strange is that the following snippet works just fine:
Firmware is version: 1.6.110079014 and the sdk version is 1.4.1. OS is Ubuntu 18.04
Do you have any suggestions for how to handle this? There is no onboard GPU, which may be the reason for the queue becoming full.