Project

General

Profile

Bug #3996

memory leaks in osmo-msc after neels/ho merge

Added by laforge 5 months ago. Updated 4 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
05/11/2019
Due date:
% Done:

100%

Resolution:

Description

I was just running a number of TTCN3 tests locally on my system and then manually stopped osmo-msc. The talloc report showed the following snippet:

    msgb                           contains  27296 bytes in  21 blocks (ref 0) 0x608000000100
        RANAP Tx                       contains   1672 bytes in   1 blocks (ref 0) 0x61c0000a98e0
        bssmap: reset ack              contains   1160 bytes in   1 blocks (ref 0) 0x61a0000288e0
        bssmap: reset ack              contains   1160 bytes in   1 blocks (ref 0) 0x61a0000282e0
        RANAP Tx                       contains   1672 bytes in   1 blocks (ref 0) 0x61c00009a8e0
        bssmap: reset ack              contains   1160 bytes in   1 blocks (ref 0) 0x61a0000228e0
        bssmap: reset ack              contains   1160 bytes in   1 blocks (ref 0) 0x61a0000222e0
        RANAP Tx                       contains   1672 bytes in   1 blocks (ref 0) 0x61c00008b0e0
        bssmap: reset ack              contains   1160 bytes in   1 blocks (ref 0) 0x61a00001c2e0
        bssmap: reset ack              contains   1160 bytes in   1 blocks (ref 0) 0x61a00001bce0
        RANAP Tx                       contains   1672 bytes in   1 blocks (ref 0) 0x61c0000708e0
        bssmap: reset ack              contains   1160 bytes in   1 blocks (ref 0) 0x61a0000180e0
        bssmap: reset ack              contains   1160 bytes in   1 blocks (ref 0) 0x61a000017ae0
        RANAP Tx                       contains   1672 bytes in   1 blocks (ref 0) 0x61c0000618e0
        RANAP Tx                       contains   1672 bytes in   1 blocks (ref 0) 0x61c0000538e0
        bssmap: reset ack              contains   1160 bytes in   1 blocks (ref 0) 0x61a00000cce0
        bssmap: reset ack              contains   1160 bytes in   1 blocks (ref 0) 0x61a00000c6e0
        RANAP Tx                       contains   1672 bytes in   1 blocks (ref 0) 0x61c0000458e0
        RANAP Tx                       contains   1672 bytes in   1 blocks (ref 0) 0x61c0000378e0
        bssmap: reset ack              contains   1160 bytes in   1 blocks (ref 0) 0x61a0000054e0
        bssmap: reset ack              contains   1160 bytes in   1 blocks (ref 0) 0x61a000004ee0

So there appears to be at least to msgb leaks: One related to BSSMAP Reset ACK (the tests have three virtual BSCs connect to the MSC), the other one related to transmission of some RANAP messages. For sure the tests were transmitting more than a total of 6 RANAP messages, i.e. it seems not every transmitted RANAP message is leaked.

History

#1 Updated by fixeria 5 months ago

  • % Done changed from 0 to 50

#2 Updated by laforge 5 months ago

On Fri, May 10, 2019 at 10:27:30PM +0000, fixeria [REDMINE] wrote:

Fixed, please see: https://git.osmocom.org/osmo-msc/commit/?id=53d3e0e54a6d9fe4356c6076cb8d064fba3b4e87

Thanks. It's not yet in gerrit for some reason, though.

#3 Updated by fixeria 5 months ago

Thanks. It's not yet in gerrit for some reason, though.

It has been already merged by Neels, please see: https://gerrit.osmocom.org/#/c/osmo-msc/+/13953/.
Do you still see the "bssmap: reset ack" memleak with the recent master? I don't see it anymore in my setup.

#4 Updated by neels 4 months ago

  • Status changed from New to Resolved
  • % Done changed from 50 to 100

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)