Taylor Boyko wrote: > My knowledge on this is a little fuzzy. It's been a while since > school when I was digging around in C memory land. > > From my understanding, PJSIP has it's own dynamic memory allocation > mechanism, meaning that it doesn't rely on the traditional c > libraries. In other words, when malloc is run, it is managed by > PJSIP, not the system. Does this sound right? > > If that's the case, then why is the pool continuously malloc'ing more > space? It must be because objects are being created in the heap and > then aren't being cleaned up (either from falling out of context, or > being free'd/delete'd). So, is the problem with the pool, or is the > problem appearing in the pool because of poor code elsewhere? > > You mention pjsua_dump. I'll play around with this and see what I can > find from it. I'm fairly determined to get this working, so I'm going > to take it as far as I can, knowledge wise. > > PJ pools are a little different. Basically you can use them to allocate memory onto the heap. That memory is associated with its pool, and does not get free'd until the entire pool is free'd. So if you do many allocations on a particular pool, there is no way to selectively free one of those allocations. You have to free the entire pool. -- Michael Broughton, Advanis Unintended Recipient & Unauthorized Use of E-Mail: This message and attachments may contain confidential or privileged information that is intended only for the named recipient of this e-mail. Any unauthorized use or distribution is not permitted. If you have received this e-mail in error, deleting the e-mail and notifying the sender would be appreciated. Thank you.
