Suspected memory leak in PCU

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/osmocom-net-gprs@lists.osmocom.org/.

Alexander Chemeris alexander.chemeris at gmail.com
Tue Jan 15 17:18:38 UTC 2013


Harald,

Thanks for the observation.

It would be great if this is filed to a bag tracker. Could you please
setup one for osmo-pcu and create this as a ticket there?

On Tue, Jan 15, 2013 at 8:42 PM, Harald Welte <laforge at gnumonks.org> wrote:
> Hi all,
>
> while running osmo-pcu, it appears that it is leaking memory.   At
> startup time it consumes 4188 kBytes of virtual memory (on sysmobts-v2),
> while after about 8MBytes of data transfer of a single GPRS-MS over 48
> hours, the virtual size has expanded to 8584 kBytes.
>
> Now I know that VSS is not RSS, etc. - but the fact that it always only
> increasees, and increases with traffic is a clear indication of some
> leakage somewehere.
>
> Unfortunately it also seems talloc is not used correctly in osmo-pcu, as
> a USR1 signal doesn't really show any allocated objects beyond two.  So
> somehow either not all allocations are done with talloc, or the
> allocation hierarchy does not link the objects to the root talloc
> context.
>
> Regards,
>         Harald
>
> --
> - Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
> ============================================================================
> "Privacy in residential applications is a desirable marketing option."
>                                                   (ETSI EN 300 175-7 Ch. A6)
>



-- 
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ООО УмРадио
http://fairwaves.ru




More information about the osmocom-net-gprs mailing list