On Mon, Mar 31, 2008 at 8:39 AM, Anshuman S. Rawat <arawat at 3clogic.com> wrote: > I think I might have something in this regard. > > In function pjsua_resolve_stun_server() in pjsua_core.c, > pj_dns_srv_resolve() is called and the pjsua_var.pool is passed as an > argument. Later in pj_dns_srv_resolve(), 'query_job' is allocated from this > pool. AFAIK, pjsau_var's pool is destroyed only when pjsua_destory() is > called. So wouldn't this cause memory leak? Yes it would. > In our case, we left our client (which uses pjsip) running overnight (for > about 12-15hrs) and noticed that memory usage had jumped from about 12K at > start to about 54K at the end of the run. We did have network outages too > during this run. Yep. And there are few other places as well where the global pool is used. I've just registered a ticket to fix this: http://trac.pjsip.org/repos/ticket/518 hopefully it'll get fixed soon. Thanks Benny > FYI, we use PJSIP at rev 1538 but I checked the latest rev at 1901 and > atleast the code is the same in both. > > Regards, > Anshuman >
