Bug #2449: memory leak in case of STP disconnect - libosmo-sccp + libosmo-sigtran - Open Source Mobile Communications

Actions

Copy link

Bug #2449

closed

memory leak in case of STP disconnect

Added by laforge over 6 years ago. Updated almost 6 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

stsp

Target version:

Start date:

08/15/2017

Due date:

% Done:

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

Copy link

Updated by laforge about 6 years ago

Assignee changed from laforge to stsp

Actions

Copy link

Updated by stsp almost 6 years ago

I can reproduce this problem with libosmo-sccp from the master branch.

After starting osmo-stp twice, the talloc report for osmo-msc shows:

    msgb                           contains   4624 bytes in   3 blocks (ref 0) 0x608000000080
    xua_asp-xlm msgb               contains   2312 bytes in   1 blocks (ref 0) 0x61d0000474e0
    xua_asp-xlm msgb               contains   2312 bytes in   1 blocks (ref 0) 0x61d00003dee0

This leak is plugged by the patch at https://gerrit.osmocom.org/#/c/8065/

Actions

Copy link