We use gjtapi in our desktop application. We have customer which heavily use the telephony capabilities of our application. These users getting memory exceptions after some hours of working. I’ve debugged a little of the gjtapi and recognized that the call-Objects created did not disposed correctly. After some Exception in the native Tapi3-API the wont be released. So with every call the memory is growing up and I don’t know what happens on the cpp side.
We use gjtapi 1.9rc1 with the latest Tapi3Provider.dll (Revision 1.7).
Hi Marcus, did you find a solution?
We have the same issue
regards
Luis
I found some memory leaks in the 1.9 RC1 DLL last fall. Please try the latest DLL from the repository or from the just uploaded 1.9 RC3.