Uploaded image for project: 'Embedded Software & Tools'
  1. Embedded Software & Tools
  2. EXT_EP-10562

Memory leak in simple_mesh_node

    XMLWordPrintable

Details

    • Bug
    • Status: Fixed
    • High
    • Resolution: Fixed
    • SimpleLink CC13x2-26x2 SDK BLE5 Stack
    • BLE_AGAMA-3460
    • BLE Stack BLE5-2.2.2
    • Hide
      BLE stack BLE5-2.2.3 RC4
      BLE Stack BLE5-2.2.3
      Show
      BLE stack BLE5-2.2.3 RC4 BLE Stack BLE5-2.2.3
    • Hide
      CC26X2R1
      CC1352R1
      CC1352P1
      CC1352P-4
      Show
      CC26X2R1 CC1352R1 CC1352P1 CC1352P-4

    Description

      Problem Description:

      About ~200 bytes of heap is lost every connection established when the simple_mesh_node project is configured for in the "Mesh and Peripheral". This eventually leads to an assert that crashes the customer's application when heap space runs out.

      SDK version tested: 5.20

      Setup:

      1. In the simple_mesh_node project, change the Mesh Application to "Mesh and Peripheral".
      2. Add HEAPMGR_METRICS to track the heapmgrMemFreeTotal while debugging
      3. Record the heapmgrMemFreeTotal before entering a connection, then enter a connection with a smartphone.
      4. Disconnect from the device and you will see that heapmgrMemFreeTotal is ~200 bytes smaller than prior to connection establishment.

      Alternate setup using Out of box firmware:

      1. Build and flash a default simple_mesh_node project.
      2. Initialize the node to advertise unprovisioned beacons.
      3. Using Lightblue, connect to the Simple mesh node and then disconnect, while recording the heapmgrMemFreeTotal. You should see the same behavior described above.

      I have verified this on my end and observe ~200 bytes (200 bytes is not exact and varies for each connection/disconnection).

      Attachments

        Activity

          People

            syncuser TI User
            syncuser TI User
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: