-
Notifications
You must be signed in to change notification settings - Fork 12
Description
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:
[11/12 20:24:51.118106][info][12988][Pipeline.cpp:411] Try to stop pipeline!
[11/12 20:24:51.118247][info][12988][Pipeline.cpp:383] Try to stop streams!
[11/12 20:25:03.137591][warning][8108][ObException.cpp:5] Resource busy! You can try again later!
[11/12 20:25:03.140114][warning][8108][FemtoBoltUvcDevice.cpp:388] Execute failure! A libobsensor_exception has occurred!
- where:388#libobsensor::FemtoBoltUvcDevice::initDepthProcessParam::<lambda_2ead263c27ab7fe23cbf81761e0b47a0>::operator ()
- msg:Resource busy! You can try again later!
- type:class libobsensor::wrong_api_call_sequence_exception
[11/12 20:25:03.140262][warning][8108][FemtoBoltUvcDevice.cpp:388] Get temperature failed.
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?