Actions
Bug #3996
closedmemory leaks in osmo-msc after neels/ho merge
Start date:
05/11/2019
Due date:
% Done:
100%
Resolution:
Spec Reference:
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.
Actions