Memory leaks
Alex Kiernan
alexk at demon.net
Mon Feb 12 16:32:52 UTC 2001
Is this an obvious one to anyone - I suspect its the enclosing object
getting freed, without its contents being freed:
New memory leaked: 55312 bytes (0.481%); potentially leaked: 2049 bytes (0.0178%)
MLK: 32784 bytes leaked in 16 blocks
* This memory was allocated from:
malloc [rtlib.o]
x_malloc [xmalloc.c:74]
ARTassignnumbers [art.c:1442]
ARTpost [art.c:2558]
NCpostit [nc.c:194]
NCproc [nc.c:972]
* Block of 2049 bytes (16 times); last block at 0x179ac90
MLK: 12288 bytes leaked in 12 blocks
* This memory was allocated from:
malloc [rtlib.o]
x_malloc [xmalloc.c:74]
ARTmakeoverview [art.c:1996]
ARTpost [art.c:2587]
NCpostit [nc.c:194]
NCproc [nc.c:972]
* Block of 1024 bytes (12 times); last block at 0x17990d0
MLK: 10240 bytes leaked in 5 blocks
* This memory was allocated from:
malloc [rtlib.o]
realloc [rtlib.o]
x_realloc [xmalloc.c:102]
ARTmakeoverview [art.c:2048]
ARTpost [art.c:2587]
NCpostit [nc.c:194]
* Block of 2048 bytes (5 times); last block at 0x1488f10
PLK: 2049 bytes potentially leaked at 0x146d678
* This memory was allocated from:
malloc [rtlib.o]
x_malloc [xmalloc.c:74]
ARTassignnumbers [art.c:1442]
ARTpost [art.c:2558]
NCpostit [nc.c:194]
NCproc [nc.c:972]
--
Alex Kiernan, Principal Engineer, Development, Thus PLC
More information about the inn-workers
mailing list