[indiana-discuss] [osol-discuss] [perf-discuss] Memory leak somewhere, maybe in libc (libc_hwcap2.so.1 / SXCE b105 x64) ?

Casper.Dik at Sun.COM Casper.Dik at Sun.COM
Thu Feb 12 00:18:38 PST 2009


>Does this explain why a wget process grew to 2.2GB (where I killed it) ??
>Then wget must have exactly the same bug, which is unlikely. Therefore
>the bug must be in a shared lib which both use. This suggests (but is
>not limited to) libc.

Run them with libumem and start them with UMEM_DEBUG set to default.

And then get a core dump (gcore) when it gets big.

Casper




More information about the indiana-discuss mailing list