-
Notifications
You must be signed in to change notification settings - Fork 7
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
Freeze in k4a_device_stop_cameras #95
Comments
At the first time, is it the user who voluntarily stops the camera causing the error, or is it the program that automatically stops the camera causing the error. |
From what I have been told, the user is not doing anything differently between the times when it works and the times when it fails. They are opening the same TouchDesigner project that is trying to connect to the Femto Bolt via the k4a wrapper library. I don't know what is triggering the attempted shutdown of the camera yet: whether it is in the k4a wrapper or something higher up in TouchDesigner. This is the full log from start up if that helps.
|
Hi, if it could help the problem started occurring the day this update was installed. So both are definitely linked: |
Any hints on what could be the problem @zzuliys maybe? |
We have a user using TouchDesigner with a Femto Bolt camera and the k4a wrapper. They are having problems where the first time they open the program it will freeze, but if they open the program again it works correctly. This issue started happening suddenly on a machine that had previously been working.
The user submitted a memory dump during the freeze and all we can tell is that it is stuck inside the wrapper version of k4a_device_stop_cameras
They also gave us the console messages before it freezes:
The rest of the startup sequence is the same between the times when it works versus the times it freezes.
We are currently using SDK version 1.10.8, wrapper version 1.10.1 and the camera has firmware 1.0.9 Unfortunately we can't update the SDK at the moment because the newest version has dependencies that conflict with other modules that we are using.
We haven't been able to reproduce this issue in a development environment, so we are relying on an user to provide information right now.
Does this sound like anything you guys are aware of? Any ideas for how we could fix this or debug it further?
The text was updated successfully, but these errors were encountered: