ymoona wrote: > The wxCommunicator indeed works nice, But it also leaking memory, after > multiple calls the memory is increased a few hundred bytes, and it won't > decrease any more > I think it is caused by the sipxtapi.dll. Another recent issue is > located at > http://list.sipfoundry.org/archive/sipx-dev/msg07011.html > I posted this issue also here: > http://list.sipfoundry.org/archive/sipxtapi-dev/msg01222.html. >
Ok I discovered a memory leak in wxCommunicator in code that reposts event to sipxtapiproxy. Container object wasn't deleted, I fixed it. After this it should be much better. There don't appear to be any other leaks in wxCommunicator, I checked it with visual leak detector 1.9f. However there are some leaks in the sipxtapi: One small leak was fixed today, and I'm proposing solution to another small leak in XPL-201. These leaks are not serious. There are also 5 other leaks: c:\work\sipxtapi\sipxportlib\src\utl\utlcontainer.cpp (32): `dynamic initializer for 'UtlContainer::spIteratorConnectionLock'' c:\work\sipxtapi\sipxportlib\src\utl\utllink.cpp (216): `dynamic initializer for 'UtlLink::spLinkPool'' c:\work\sipxtapi\sipxportlib\src\utl\utllink.cpp (351): `dynamic initializer for 'UtlPair::spPairPool'' c:\work\sipxtapi\sipxportlib\src\os\osnamedb.cpp (31): `dynamic initializer for 'OsNameDb::spLock'' c:\work\sipxtapi\sipxportlib\src\os\ostimertask.cpp (37): `dynamic initializer for 'OsTimerTask::sLock'' These are also constant leaks and are not serious. I will try visual leak detector 1.0 as I think 1.9f doesn't properly detect all leaks from sipxtapi, I can see in visual studio 2005 debugging window parts of SIP messages after program exists. I think this might be the same problem you have. Jaroslav Libak _______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
