[postgis-devel] malloc/palloc/lwalloc

Paul Ramsey pramsey at cleverelephant.ca
Wed Sep 24 14:51:53 PDT 2008


If I knew the problem was limited to liblwgeom, that might be
possible. But I don't.

P.

On Wed, Sep 24, 2008 at 2:37 PM, strk <strk at keybit.net> wrote:
> On Tue, Sep 23, 2008 at 11:28:34PM -0700, Paul Ramsey wrote:
>> Tom,
>>
>> Since I have you here...
>>
>> I've been trying to track down memory leaks in PostGIS code, and the
>> power of palloc is getting in my way... since palloc handles all the
>> memory cleanly, valgrind thinks that the code is leakless, which it
>> is, from a system point-of-view, but it also, clearly leaks.
>>
>> Ordinarily, this might be fine ("so what, it leaks, it'll get cleaned
>> up in the end") but in our case, we are leaking so *much* memory that
>> the database actually OOMs on some big workloads. Hence the leak hunt,
>> but a difficult hunt, without supporting tools.
>>
>> Any ideas on tools / tricks?
>
> Avoid postgres and use straight liblwgeom ?
>
> --strk;
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel
>



More information about the postgis-devel mailing list