<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Other NXP Products中的主题 Problem on Memory allocation: MsgTrackingArray</title>
    <link>https://community.nxp.com/t5/Other-NXP-Products/Problem-on-Memory-allocation-MsgTrackingArray/m-p/390547#M3210</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm using Beekit solution on MC13213.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I observed many problem with result of&amp;nbsp; MsgTrackingArray&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) After call App_StartCoordinator, and acknowledge MLME Send Association Indication, it still One memory place not empty: (Small = 5, Big = 5)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;BLOCKQUOTE&gt;
&lt;P&gt;0 -. MsgAddr:08B1. AllocAddr:1F16. FreeAddr:516C. AllocCounter:01. FreeCounter:01&lt;/P&gt;
&lt;P&gt;1 -. MsgAddr:08CB. AllocAddr:559B. FreeAddr:33BC. AllocCounter:01. FreeCounter:01&lt;/P&gt;
&lt;P&gt;2 -. MsgAddr:08E5. AllocAddr:5588. FreeAddr:1DF9. AllocCounter:01. FreeCounter:01&lt;/P&gt;
&lt;P&gt;3 -. MsgAddr:08FF. AllocAddr:0000. FreeAddr:0000. AllocCounter:00. FreeCounter:00&lt;/P&gt;
&lt;P&gt;4 -. MsgAddr:0919. AllocAddr:0000. FreeAddr:0000. AllocCounter:00. FreeCounter:00&lt;/P&gt;
&lt;P&gt;5 -. MsgAddr:0933. AllocAddr:0000. FreeAddr:0000. AllocCounter:00. FreeCounter:00&lt;/P&gt;
&lt;P&gt;6 -. MsgAddr:09BD. AllocAddr:0000. FreeAddr:0000. AllocCounter:00. FreeCounter:00&lt;/P&gt;
&lt;P&gt;7 -. MsgAddr:0A47. AllocAddr:0000. FreeAddr:0000. AllocCounter:00. FreeCounter:00&lt;/P&gt;
&lt;P&gt;8 -. MsgAddr:0AD1. AllocAddr:0000. FreeAddr:0000. AllocCounter:00. FreeCounter:00&lt;/P&gt;
&lt;P&gt;9 A. MsgAddr:0B5B. AllocAddr:6A1C. FreeAddr:0000. AllocCounter:01. FreeCounter:00&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The last case is not free and will stay always allocated!&lt;/P&gt;&lt;P&gt;The MSG_Free(pMsgIn) is well called after App_HandleMlmeInput, but before this, number of allocated memory is 2. Then the MSG_Free free one of these two but still one!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What can be the root cause of this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After in the code live, If I made &lt;STRONG&gt;many&lt;/STRONG&gt; Association request with Negative response&lt;/P&gt;&lt;P&gt; (App_SendAssociateResponse -&amp;gt; pAssocRes-&amp;gt;status = gPanAccessDenied then memory allocation become full after some time.&lt;/P&gt;&lt;P&gt;ANd then buffer is full then all request are rejected because Memory allocation is rejected!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Did you have an idea why Beestack does not free memory allocation?:smileyhappy:&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 17 Mar 2015 15:02:08 GMT</pubDate>
    <dc:creator>arnogir</dc:creator>
    <dc:date>2015-03-17T15:02:08Z</dc:date>
    <item>
      <title>Problem on Memory allocation: MsgTrackingArray</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/Problem-on-Memory-allocation-MsgTrackingArray/m-p/390547#M3210</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm using Beekit solution on MC13213.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I observed many problem with result of&amp;nbsp; MsgTrackingArray&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) After call App_StartCoordinator, and acknowledge MLME Send Association Indication, it still One memory place not empty: (Small = 5, Big = 5)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;BLOCKQUOTE&gt;
&lt;P&gt;0 -. MsgAddr:08B1. AllocAddr:1F16. FreeAddr:516C. AllocCounter:01. FreeCounter:01&lt;/P&gt;
&lt;P&gt;1 -. MsgAddr:08CB. AllocAddr:559B. FreeAddr:33BC. AllocCounter:01. FreeCounter:01&lt;/P&gt;
&lt;P&gt;2 -. MsgAddr:08E5. AllocAddr:5588. FreeAddr:1DF9. AllocCounter:01. FreeCounter:01&lt;/P&gt;
&lt;P&gt;3 -. MsgAddr:08FF. AllocAddr:0000. FreeAddr:0000. AllocCounter:00. FreeCounter:00&lt;/P&gt;
&lt;P&gt;4 -. MsgAddr:0919. AllocAddr:0000. FreeAddr:0000. AllocCounter:00. FreeCounter:00&lt;/P&gt;
&lt;P&gt;5 -. MsgAddr:0933. AllocAddr:0000. FreeAddr:0000. AllocCounter:00. FreeCounter:00&lt;/P&gt;
&lt;P&gt;6 -. MsgAddr:09BD. AllocAddr:0000. FreeAddr:0000. AllocCounter:00. FreeCounter:00&lt;/P&gt;
&lt;P&gt;7 -. MsgAddr:0A47. AllocAddr:0000. FreeAddr:0000. AllocCounter:00. FreeCounter:00&lt;/P&gt;
&lt;P&gt;8 -. MsgAddr:0AD1. AllocAddr:0000. FreeAddr:0000. AllocCounter:00. FreeCounter:00&lt;/P&gt;
&lt;P&gt;9 A. MsgAddr:0B5B. AllocAddr:6A1C. FreeAddr:0000. AllocCounter:01. FreeCounter:00&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The last case is not free and will stay always allocated!&lt;/P&gt;&lt;P&gt;The MSG_Free(pMsgIn) is well called after App_HandleMlmeInput, but before this, number of allocated memory is 2. Then the MSG_Free free one of these two but still one!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What can be the root cause of this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After in the code live, If I made &lt;STRONG&gt;many&lt;/STRONG&gt; Association request with Negative response&lt;/P&gt;&lt;P&gt; (App_SendAssociateResponse -&amp;gt; pAssocRes-&amp;gt;status = gPanAccessDenied then memory allocation become full after some time.&lt;/P&gt;&lt;P&gt;ANd then buffer is full then all request are rejected because Memory allocation is rejected!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Did you have an idea why Beestack does not free memory allocation?:smileyhappy:&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Mar 2015 15:02:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/Problem-on-Memory-allocation-MsgTrackingArray/m-p/390547#M3210</guid>
      <dc:creator>arnogir</dc:creator>
      <dc:date>2015-03-17T15:02:08Z</dc:date>
    </item>
    <item>
      <title>Re: Problem on Memory allocation: MsgTrackingArray</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/Problem-on-Memory-allocation-MsgTrackingArray/m-p/390548#M3211</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In fact, MsgTrackingArray is allocated when Mlme message received and Association response send, but never Desallocated after. Array is desallocated only when an Mcps message is Received/Sent.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then If I made many association without any Mcps message, array become full!...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are they a way to correct this problem?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank&lt;/P&gt;&lt;P&gt;:smileyconfused:&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Mar 2015 13:32:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/Problem-on-Memory-allocation-MsgTrackingArray/m-p/390548#M3211</guid>
      <dc:creator>arnogir</dc:creator>
      <dc:date>2015-03-18T13:32:06Z</dc:date>
    </item>
    <item>
      <title>Re: Problem on Memory allocation: MsgTrackingArray</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/Problem-on-Memory-allocation-MsgTrackingArray/m-p/390549#M3212</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anybody have an idea to resolve memory allocation problem?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 Apr 2015 05:27:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/Problem-on-Memory-allocation-MsgTrackingArray/m-p/390549#M3212</guid>
      <dc:creator>arnogir</dc:creator>
      <dc:date>2015-04-01T05:27:43Z</dc:date>
    </item>
    <item>
      <title>Re: Problem on Memory allocation: MsgTrackingArray</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/Problem-on-Memory-allocation-MsgTrackingArray/m-p/390550#M3213</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I updated stack with beestack v3.0.2.&lt;/P&gt;&lt;P&gt;No problem occurs now, buffer allocation is well empty.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 May 2015 13:08:55 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/Problem-on-Memory-allocation-MsgTrackingArray/m-p/390550#M3213</guid>
      <dc:creator>arnogir</dc:creator>
      <dc:date>2015-05-26T13:08:55Z</dc:date>
    </item>
  </channel>
</rss>

