tree 1b0b50f3524bc03b28b9b6e9f733f79dcda6dda8
parent c9dbe3c7b1fef1a4132a2415d3e74a04591735c9
author Holger Hans Peter Freyther <holger@moiji-mobile.com> 1439379346 +0200
committer Holger Hans Peter Freyther <holger@moiji-mobile.com> 1439379502 +0200

sms: Attempt to plug memory leaks seen at Rhizomatica

Using the talloc leak report we see that there are some msgb's
that are allocated for SMS but we don't have transactions or
SMS around. We need to improve the name of the messages to
uniquely dscribe where they are from but the obvious leak does
occur in this routine.

The no available transaction id is most likely the case where
we leak memory. This should not occur and shows another issue
with the smsqueue/smpp handling. It doesn't explain the subscr
reference count issue either.

Extract of the leak report:

  GSM 04.11                      contains   1160 bytes in   1 blocks (ref 0) 0x2517dc0
  GSM 04.11                      contains   1160 bytes in   1 blocks (ref 0) 0x24b56e0
  GSM 04.11                      contains   1160 bytes in   1 blocks (ref 0) 0x23e7930