- 04/11/2014 at 10:14 #1965
When I try to call txInitializeEyeX again after successfully shutting it down with txUninitializeEyeX (which returns TX_RESULT_OK), I get an APIException thrown. Why does it happen? I really need a runtime option to fully disable everything related to eye tracking and re-enable it at any time.04/11/2014 at 17:05 #1970
Update: re-tested with the new SDK (wasn’t aware of the recent update). Second txInitializeEyeX actually “fails” with TX_RESULT_EYEXALREADYINITIALIZED, although a previous txUninitializeEyeX was successful. Everything else seems to work afterwards (as far as I can tell right now).
Also, the exceptions which previously confused me seem to be correctly caught by the API itself (I was debugging with breaking on every exception), so that was a false alarm.
Still, looks like something isn’t being cleaned up properly on uninitialize.05/11/2014 at 16:33 #1974Jenny [Tobii]Participant
Hm, this sounds like a bug. We’ll try and reproduce it.06/11/2014 at 14:58 #1977Jenny [Tobii]Participant
We managed to reproduce the problem, and there is a bug.
But, it only appears under the circumstance that there are EyeX interaction objects that have not been cleaned up correctly in the client application before uninitializing EyeX. That is, when there are TX_HANDLE objects that have not been released using txReleaseObject (or TX_CONTEXTHANDLE not released by txReleaseContext).
So, you most likely have objects that are leaking in your application!
You can check this by checking the return value from
txShutdownContext(hContext, TX_CLEANUPTIMEOUT_DEFAULT, TX_FALSE);
If it returns TX_RESULT_OBJECTLEAKAGE then there are objects leaking. Then, please make sure you are using txReleaseObject for all TX_HANDLEs you are setting up. (See the MinimalGazeDataStream sample for an example how to do this.)
Our EyeX Engine team will fix the bug so that it will not be possible to end up in the inconsistent state you saw, even when objects have not been cleaned up correctly by the client application.06/11/2014 at 15:23 #1979
Thanks for the info. It turns out that I really forgot to release some handles in event handlers. Works fine now.
- You must be logged in to reply to this topic.