-
Notifications
You must be signed in to change notification settings - Fork 1.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
Libusb Errors Leading to Node Crash #3245
Comments
Hi @BryanBetancur Does it make a difference if you add initial_reset:=true to the launch instruction to reset the camera at launch, please? |
Thanks for your quick response, I will check it during the day. |
It continues happening with the initial_reset:=true.
|
Would it be possible for you to check Ubuntu's htop system monitoring tool to see whether the available memory capacity of the computer reduces after each start-stop? If it does then this is called a 'memory leak' and once enough of the memory has been consumed then a program can become unstable or freeze / exit. |
Hello
Issue Description
After enabling and disabling the camera multiple times, the following errors occur randomly, causing the node to crash and subsequently respawn. I've documented three different cases (but all related with libusb), which I'll outline below:
The only thing I’ve been able to identify is that it happens after the logs of
(messenger-libusb.cpp:42) control_transfer returned error, index: 768, error: Resource temporarily unavailable, number: 11
, which occur quite frequently. I would appreciate it if you could guide me on how to resolve this issue.The text was updated successfully, but these errors were encountered: