This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

GATT Service Memory Management

I am writing my own profile to exchange a small uint8 arrray.  My application checks to make sure the array writing to the peripheral by the central is a valid value based on a look-up table.   Following the Device Info Profile I use osal_memcpy() within the profile to transfer data in the WriteCB function.  Similar in the Get_Param and Set_Param functions.  I noticed in the Device Info Profile that although the osal_memcpy() is used in the Set_Param function, to set the GATT value based on a temporary pointers data, there is no osal_mem_free() function used to release the memory that was taken by the temporary pointer.  Is this handled by lower level object code, or is it simply freed properly because the pointer only exists within the function?    Thanks Guys

P.S. In double checking my memory management, I did notice if I used osal_mem_free() after the osal_memcpy() of the data at the temporary pointer, for some reason my memAlo = 65K????