Actions
Bug #2449
closedmemory leak in case of STP disconnect
Start date:
08/15/2017
Due date:
% Done:
0%
Spec Reference:
Description
we're leaking one msgb in the client (e.g. OsmoMSC) every time the STP-client connection is released:
msgb contains 11560 bytes in 6 blocks (ref 0) 0x5611734710e0
xua_asp-xlm msgb contains 2312 bytes in 1 blocks (ref 0) 0x561173553930
xua_asp-xlm msgb contains 2312 bytes in 1 blocks (ref 0) 0x561173552fc0
xua_asp-xlm msgb contains 2312 bytes in 1 blocks (ref 0) 0x561173552650
xua_asp-xlm msgb contains 2312 bytes in 1 blocks (ref 0) 0x561173551ce0
xua_asp-xlm msgb contains 2312 bytes in 1 blocks (ref 0) 0x561173551370
the above is after 6 connect/disconnect cycles.
- After start of the client, there is no msgb allocated.
- After successful M3UA connection to STP, one such msgb is allocated
- After M3UA disconnect (STP disappeared), the msgb is still allocated
Actions
