Memory leaks

Alex Kiernan alexk at
Tue Feb 13 08:25:11 UTC 2001

Katsuhiro Kondou <kondou at> writes:

> In article <723ddjhnez.fsf at>,
> 	Alex Kiernan <alexk at> wrote;
> } Is this an obvious one to anyone - I suspect its the enclosing object
> } getting freed, without its contents being freed:
> No, they never be freed.  The region(ARTDATA *data) is actually
> static area(included in CHANNEL), and holding pointer and size
> are never cleared even if the channel is closed.

How about the channel - does that get freed (actually I think I've
just seen where the problem could be). This morning we're up to over
1MB of leaked memory, plus a couple of out of array bounds reads and
an uninitialised memory read - I'll post them in a separate messaage.

Alex Kiernan, Principal Engineer, Development, Thus PLC

More information about the inn-workers mailing list