-
Notifications
You must be signed in to change notification settings - Fork 16
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
Orbbec SDK hanging on std::exit #12
Comments
If I change the closing sequence to have some printouts this is the output from:
Note: I have tried not closing the pipe or resetting too. |
I believe the issue is related to a deadlock caused by the code I wrote to prevent the spdlog crash problem. The registry instance of spdlog is a static object, and it needs to be ensured that no log output remains after the object is destroyed when the program exits. Therefore, I cached the object and added a lock to avoid this situation. This issue has been resolved in the recent version. May you can verifiy it using v1.7.5. |
Having a lot of fun with the SDK with the Femto Mega.
One issue I can't seem to resolve is that when my app closes I get a hang no matter how I seem to close it.
Is there a rule in terms of what objects need to get destroyed first?
Or what objects you have to hang onto ( as shared_ptr's ) and what ones you can use just for opening the device?
I should note that my app works great until I try and close it or if I manually call std:exit(0);
I have tried a lot of different combos, but can't get anything working that isn't a single main(){ style app.
Below is my app ( simplified ), it also uses GLFW for windowing and setup and update are all on the main thread.
The text was updated successfully, but these errors were encountered: