Problem on Memory allocation: MsgTrackingArray

[arnogir]

Hello

I'm using Beekit solution on MC13213.

I observed many problem with result of  MsgTrackingArray

1) After call App_StartCoordinator, and acknowledge MLME Send Association Indication, it still One memory place not empty: (Small = 5, Big = 5)

0 -. MsgAddr:08B1. AllocAddr:1F16. FreeAddr:516C. AllocCounter:01. FreeCounter:01

1 -. MsgAddr:08CB. AllocAddr:559B. FreeAddr:33BC. AllocCounter:01. FreeCounter:01

2 -. MsgAddr:08E5. AllocAddr:5588. FreeAddr:1DF9. AllocCounter:01. FreeCounter:01

3 -. MsgAddr:08FF. AllocAddr:0000. FreeAddr:0000. AllocCounter:00. FreeCounter:00

4 -. MsgAddr:0919. AllocAddr:0000. FreeAddr:0000. AllocCounter:00. FreeCounter:00

5 -. MsgAddr:0933. AllocAddr:0000. FreeAddr:0000. AllocCounter:00. FreeCounter:00

6 -. MsgAddr:09BD. AllocAddr:0000. FreeAddr:0000. AllocCounter:00. FreeCounter:00

7 -. MsgAddr:0A47. AllocAddr:0000. FreeAddr:0000. AllocCounter:00. FreeCounter:00

8 -. MsgAddr:0AD1. AllocAddr:0000. FreeAddr:0000. AllocCounter:00. FreeCounter:00

9 A. MsgAddr:0B5B. AllocAddr:6A1C. FreeAddr:0000. AllocCounter:01. FreeCounter:00

The last case is not free and will stay always allocated!

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!

What can be the root cause of this?

After in the code live, If I made many Association request with Negative response

(App_SendAssociateResponse -> pAssocRes->status = gPanAccessDenied then memory allocation become full after some time.

ANd then buffer is full then all request are rejected because Memory allocation is rejected!

Did you have an idea why Beestack does not free memory allocation?:smileyhappy:

[arnogir]

Hello

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.

Then If I made many association without any Mcps message, array become full!...

Are they a way to correct this problem?

Thank

:smileyconfused:

[arnogir]

Hello

Anybody have an idea to resolve memory allocation problem?

[arnogir · Accepted solution]

I updated stack with beestack v3.0.2.

No problem occurs now, buffer allocation is well empty.