Wow! I build the latest build from the SIPXtapi repo, I ran the place call example and I got only 12 memory leaks, that's great! With the media-update branch I got over 400 leaks! Are there so many leaks fixed or is the leak detector not able to detect these leaks in this version of SipX
2007/5/8, Jaroslav Libák <[EMAIL PROTECTED]>:
>In stead of making the private static memeber public I should add a function the creates the instance and add a function that deletes >the instance correct? I'm currently compiling the latest version from http://scm.sipfoundry.org/rep/sipX/branches/sipXtapi (9488) Yes, add static methods that initialize and deinitialize private static members. Then call these functions from portlib init/shutdown methods. Jaro _______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
_______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
