<div dir="ltr">FreeSWITCH uses memory pools, the session has its own pool that is used for all of its key resources.  The apr objects like mutexes register a destroy function with the pool when they are created and when you destroy the pool after the session has ended it cleans up the memory.<div>
<br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jul 23, 2013 at 8:08 AM, Ken Rice <span dir="ltr">&lt;<a href="mailto:krice@freeswitch.org" target="_blank">krice@freeswitch.org</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div><br>this is a perfect example of what you should open a ticket on jira....</div><div><br></div><div>
<br></div><div><br><div>Ken</div>Sent from my iPad</div><div><div class="h5"><div><br>On Jul 23, 2013, at 6:55, hkchoi &lt;<a href="mailto:linuxsarang@naver.com" target="_blank">linuxsarang@naver.com</a>&gt; wrote:<br><br>
</div><blockquote type="cite"><div><div style="font-size:10pt;font-family:Gulim"><p>Hello freeswitch-users, </p><p> </p><p>there is some doubt about memory leak in freeswitch implemetation.</p><p> </p><p>when a channel is created, some mutex are created as below.</p>
<p style="font-size:10pt"> </p><p style="font-size:10pt">SWITCH_DECLARE(switch_status_t) switch_channel_alloc(switch_channel_t **channel, switch_call_direction_t direction, switch_memory_pool_t *pool)<br>{<br>    switch_assert(pool != NULL);</p>
<p style="font-size:10pt">    if (((*channel) = switch_core_alloc(pool, sizeof(switch_channel_t))) == 0) {<br>        return SWITCH_STATUS_MEMERR;<br>    }</p><p style="font-size:10pt">    switch_event_create_plain(&amp;(*channel)-&gt;variables, SWITCH_EVENT_CHANNEL_DATA);</p>
<p style="font-size:10pt">    switch_core_hash_init(&amp;(*channel)-&gt;private_hash, pool);<br>    switch_queue_create(&amp;(*channel)-&gt;dtmf_queue, SWITCH_DTMF_LOG_LEN, pool);<br>    switch_queue_create(&amp;(*channel)-&gt;dtmf_log_queue, SWITCH_DTMF_LOG_LEN, pool);</p>
<p style="font-size:10pt">    switch_mutex_init(&amp;(*channel)-&gt;dtmf_mutex, SWITCH_MUTEX_NESTED, pool);<br>    switch_mutex_init(&amp;(*channel)-&gt;flag_mutex, SWITCH_MUTEX_NESTED, pool);<br>    switch_mutex_init(&amp;(*channel)-&gt;state_mutex, SWITCH_MUTEX_NESTED, pool);<br>
    switch_mutex_init(&amp;(*channel)-&gt;thread_mutex, SWITCH_MUTEX_NESTED, pool);<br>    switch_mutex_init(&amp;(*channel)-&gt;profile_mutex, SWITCH_MUTEX_NESTED, pool);<br>    ...</p><p style="font-size:10pt">}</p><p> </p>
<p style="font-size:10pt">And,  It seems that some memory is newly allocated in switch_mutex_init() by comments in the following code.</p><p style="font-size:10pt"> </p><p style="font-size:10pt">[ switch_apr.h ]</p><p style="font-size:10pt">
/**<br> * Create and initialize a mutex that can be used to synchronize threads.<br> * @param lock the memory address where the newly created mutex will be<br> *        stored.<br> * @param flags Or&#39;ed value of:<br> * &lt;PRE&gt;<br>
 *           SWITCH_THREAD_MUTEX_DEFAULT   platform-optimal lock behavior.<br> *           SWITCH_THREAD_MUTEX_NESTED    enable nested (recursive) locks.<br> *           SWITCH_THREAD_MUTEX_UNNESTED  disable nested locks (non-recursive).<br>
 * &lt;/PRE&gt;<br> * @param pool the pool from which to allocate the mutex.<br> * @warning Be cautious in using SWITCH_THREAD_MUTEX_DEFAULT.  While this is the<br> * most optimial mutex based on a given platform&#39;s performance charateristics,<br>
 * it will behave as either a nested or an unnested lock.<br> *<br>*/<br>SWITCH_DECLARE(switch_status_t) switch_mutex_init(switch_mutex_t ** lock, unsigned int flags, switch_memory_pool_t *pool);</p><p style="font-size:10pt">
<br>/**<br> * Destroy the mutex and free the memory associated with the lock.<br> * @param lock the mutex to destroy.<br> */<br>SWITCH_DECLARE(switch_status_t) switch_mutex_destroy(switch_mutex_t *lock); </p><p style="font-size:10pt">
but, I can&#39;t find any code that is related with destroying mutex.</p><p style="font-size:10pt"> </p><p style="font-size:10pt">In my opinion, </p><p style="font-size:10pt">altough a memory size is very tiny for creating mutex, the leaking memory will be more bigger as times go on.</p>
<p style="font-size:10pt"> </p><p style="font-size:10pt">It doesn&#39;t need to destory the mutex when a channel is destory?</p><p style="font-size:10pt"> </p><p style="font-size:10pt">could someone explain about this?</p>
<p style="font-size:10pt"> </p><p style="font-size:10pt">Thank you in advance.</p><p style="font-size:10pt"> </p><p style="font-size:10pt">Regards,</p><p style="font-size:10pt">hkchoi</p></div>
<table><tbody><tr><td><img src="http://mail.naver.com/readReceipt/notify/?img=oeFqDHk516mYar%2B5MBiCpzElaA2Za6MXMxtZFxCoKo%2BCpxkSFqpoF6k0MoJoKxJg%2BH%2B0Mouq74lR74lcWNFlbX30WLloWrdQarpZp6kq%2Br0dMr2R%2BBF0bNFgWz0q%2BHK5pNi0pBFX1B3o1VlTb4b%3D.gif" border="0"></td>
</tr></tbody></table></div></blockquote></div></div><blockquote type="cite"><div><span>_________________________________________________________________________</span><br><span>Professional FreeSWITCH Consulting Services:</span><br>
<span><a href="mailto:consulting@freeswitch.org" target="_blank">consulting@freeswitch.org</a></span><br><span><a href="http://www.freeswitchsolutions.com" target="_blank">http://www.freeswitchsolutions.com</a></span><br>
<span></span><br><span>FreeSWITCH-powered IP PBX: The CudaTel Communication Server</span><br><span><a href="http://www.cudatel.com" target="_blank">http://www.cudatel.com</a></span><br><span></span><br><span>Official FreeSWITCH Sites</span><br>
<span><a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a></span><br><span><a href="http://wiki.freeswitch.org" target="_blank">http://wiki.freeswitch.org</a></span><br><span><a href="http://www.cluecon.com" target="_blank">http://www.cluecon.com</a></span><br>
<span></span><br><span>FreeSWITCH-users mailing list</span><br><span><a href="mailto:FreeSWITCH-users@lists.freeswitch.org" target="_blank">FreeSWITCH-users@lists.freeswitch.org</a></span><br><span><a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a></span><br>
<span>UNSUBSCRIBE:http://<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">lists.freeswitch.org/mailman/options/freeswitch-users</a></span><br><span><a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a></span><br>
</div></blockquote></div><br>_________________________________________________________________________<br>
Professional FreeSWITCH Consulting Services:<br>
<a href="mailto:consulting@freeswitch.org">consulting@freeswitch.org</a><br>
<a href="http://www.freeswitchsolutions.com" target="_blank">http://www.freeswitchsolutions.com</a><br>
<br>
FreeSWITCH-powered IP PBX: The CudaTel Communication Server<br>
<a href="http://www.cudatel.com" target="_blank">http://www.cudatel.com</a><br>
<br>
Official FreeSWITCH Sites<br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<a href="http://wiki.freeswitch.org" target="_blank">http://wiki.freeswitch.org</a><br>
<a href="http://www.cluecon.com" target="_blank">http://www.cluecon.com</a><br>
<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Anthony Minessale II<br><br>FreeSWITCH <a href="http://www.freeswitch.org/">http://www.freeswitch.org/</a><br>ClueCon <a href="http://www.cluecon.com/">http://www.cluecon.com/</a><br>
Twitter: <a href="http://twitter.com/FreeSWITCH_wire">http://twitter.com/FreeSWITCH_wire</a><br><br>AIM: anthm<br><a href="mailto:MSN%3Aanthony_minessale@hotmail.com">MSN:anthony_minessale@hotmail.com</a><br>GTALK/JABBER/<a href="mailto:PAYPAL%3Aanthony.minessale@gmail.com">PAYPAL:anthony.minessale@gmail.com</a><br>
IRC: <a href="http://irc.freenode.net">irc.freenode.net</a> #freeswitch<br><br>FreeSWITCH Developer Conference<br><a href="mailto:sip%3A888@conference.freeswitch.org">sip:888@conference.freeswitch.org</a><br><a href="mailto:googletalk%3Aconf%2B888@conference.freeswitch.org">googletalk:conf+888@conference.freeswitch.org</a><br>
pstn:+19193869900
</div>