Home › Forums › Software Development › Tobii EyeX Engine Lockup and Possible Memory Leak
Tagged: @Grant
- This topic has 5 replies, 2 voices, and was last updated 6 years, 7 months ago by
Grant [Tobii].
- AuthorPosts
- 04/10/2016 at 19:10 #5753
R
ParticipantHi,
I have modified the MinimalStatusNotifications.c file from the C++ SDK to reproduce an issue we ran across in our development. After many connections and disconnections (~1000-2000) from the engine, it a) appears to leak memory b) eventually gets into a state where calling the cleanup functions (txShutdownContext, txReleaseContext, txUninitializeEyeX) will hang. When I open Windows TaskMgr while this sample is running, I see “Tobii EyeX Engine (32 bit)” is running and gets up to ~106MB of memory before the condition occurs. It starts out at ~48MB. Is there an easy way to get you the modified file to reproduce what I’m seeing?
The EyeX Engine version I currently have installed is 1.9.4.6493.
Thanks
05/10/2016 at 11:47 #5756Grant [Tobii]
KeymasterHi @randr, thanks for your diligence. One of our customer support agents will be in touch with directly to discuss this.
21/10/2016 at 13:18 #5856Grant [Tobii]
KeymasterHi @randr, we have confirmed the presence of a memory leak when using a high number of connection. We intend to fix this in an upcoming release. Many thanks for reporting this!
10/02/2017 at 01:09 #6318R
ParticipantHi
10/02/2017 at 01:10 #6319R
ParticipantHi @Grant,
Can you let me know what components and versions need to be updated to resolve this issue?
Thank you!
12/02/2017 at 20:10 #6326Grant [Tobii]
KeymasterHi @randr, sure thing.. please uninstall all existing Tobii software on your system and upgrade to the latest Tobii Interaction Engine and Eye Tracker Drivers Bundle which you can get @ http://developer.tobii.com/downloads/
Kindly let us know how it goes.
- AuthorPosts
- You must be logged in to reply to this topic.