Project

General

Profile

Bug #2780

OsmoBSC memory leak on bsc_subscriber

Added by laforge about 3 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
A interface
Target version:
-
Start date:
12/22/2017
Due date:
% Done:

100%

Spec Reference:

Description

After one complete iteration of the BSC_Tests TTCN-3 testsuite, we have a number of stale bsc_subscr entries that should have been cleaned up:

        struct llist_head              contains    592 bytes in  13 blocks (ref 0) 0x84a5e80
            struct bsc_subscr              contains     48 bytes in   1 blocks (ref 0) 0x94e59b0
            struct bsc_subscr              contains     48 bytes in   1 blocks (ref 0) 0x935b030
            struct bsc_subscr              contains     48 bytes in   1 blocks (ref 0) 0x91c8210
            struct bsc_subscr              contains     48 bytes in   1 blocks (ref 0) 0x9060b80
            struct bsc_subscr              contains     48 bytes in   1 blocks (ref 0) 0x8f9fc20
            struct bsc_subscr              contains     48 bytes in   1 blocks (ref 0) 0x8e907a0
            struct bsc_subscr              contains     48 bytes in   1 blocks (ref 0) 0x8c4d700
            struct bsc_subscr              contains     48 bytes in   1 blocks (ref 0) 0x8adf270
            struct bsc_subscr              contains     48 bytes in   1 blocks (ref 0) 0x8955180
            struct bsc_subscr              contains     48 bytes in   1 blocks (ref 0) 0x870f830
            struct bsc_subscr              contains     48 bytes in   1 blocks (ref 0) 0x86045d0
            struct bsc_subscr              contains     48 bytes in   1 blocks (ref 0) 0x9b7c0d0

History

#1 Updated by laforge about 3 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 10

After applying https://gerrit.osmocom.org/5554 to get the "show subscriber all" comand,
I get the following output:

OsmoBSC> show subscriber all 
 IMSI             TMSI     LAC    Use
  001010123456789  ffffffff  65534  3
  001010100000001  a1b2c301  65534  1
  001010100000002  a1b2c302  65534  1
  001010100000003  a1b2c303  65534  1
  001010000000004  a1b2c304  65534  1
  001010000000005  a1b2c305  65534  1
  001010000000006  ffffffff  65534  1
  001010000000007  ffffffff  65534  1
  001010000000008  ffffffff  65534  1
  001010000000009  ffffffff  65534  1
  001010000000010  ffffffff      1  1
  001010000000011  ffffffff  65534  1

It seems they are directly related to the paging tests. We must have a ref count leak in there.

#2 Updated by laforge about 3 years ago

  • Category set to A interface
  • Status changed from In Progress to Closed
  • % Done changed from 10 to 100

refcount leak found in BSSMAP PAGING code. Fixed in https://gerrit.osmocom.org/5555

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)