Project

General

Profile

Feature #3913

allow applications to override libsmpp34 memory allocation

Added by laforge about 2 months ago. Updated about 2 months ago.

Status:
In Progress
Priority:
Normal
Assignee:
Target version:
-
Start date:
04/09/2019
Due date:
% Done:

90%

Spec Reference:

Description

As we have seen in #3910 / #3912, we've had smpp related memory leaks for ages, as we assume all our heap allocations are seen in the talloc report. This isn't true for libsmpp34 which calls malloc() and free() directly.

Let's introduce a mechanism by which libsmpp34-using applications can override the memory allocator functions.


Related issues

Related to OsmoMSC - Bug #3912: memory leak in SMPP interfaceResolved2019-04-09

History

#1 Updated by laforge about 2 months ago

  • Related to Bug #3912: memory leak in SMPP interface added

#2 Updated by laforge about 2 months ago

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

Patch in https://gerrit.osmocom.org/#/c/libsmpp34/+/13561

We need to make sure to do the talloc integration in osmo-msc, once this is merged.

#3 Updated by laforge about 2 months ago

  • % Done changed from 100 to 90

https://gerrit.osmocom.org/#/c/osmo-msc/+/13562 implements the actual talloc integration in osmo-msc

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)