[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lynx-dev Memory leaks in dev.16

From: Klaus Weide
Subject: Re: lynx-dev Memory leaks in dev.16
Date: Sat, 11 Dec 1999 14:54:28 -0600 (CST)

On Sat, 11 Dec 1999, Michael Warner wrote:

> I guess find-leaks found a couple, after all:
> Memory leak detected.
> Pointer:      1400c7540
> Contains:     y|e you sure you want to quit?|x.asp?MediaSource=h
> ByteSize:     256
> FileName:     ../../../WWW/Library/Implementation/HTString.c
> LineCount:    492
> Memory leak detected.
> Pointer:      1400c7f40
> Contains:     %c|04s||||||||||||||||||||||||||||||||||||||||||||
> ByteSize:     280
> FileName:     ../../../WWW/Library/Implementation/HTString.c
> LineCount:    492
> realloced:    ../../../WWW/Library/Implementation/HTString.c
> LineCount:    490
> Total memory leakage this run:        536

Ah yes, these are the result of

 * If SAVE_TIME_NOT_SPACE is defined, StrAllocVsprintf will hang on to
 * its temporary string buffers instead of allocating and freeing them
 * in each invocation.  They only grow and never shrink, and won't be
 * cleaned up on exit. - kw

IOW two intentional leaks.  That could be worked around, but leaving them
as "leaks" allows to see (with leak tracking) how much memory is affected
by keeping those buffers allocated (536 = very little in this case).

As long as you only see those two in HTString.c, and the total
doesn't get huge, things are fine.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]