Jan Vroonhof <vroonhof(a)math.ethz.ch> wrote:
Darryl Okahata <darrylo(a)sr.hp.com> writes:
> [2 leaks <text/plain; US-ASCII (quoted-printable)>]
> MLK: 304000 bytes leaked at 0x401bc638
> * This memory was allocated from:
> malloc [rtlib.o]
> xmalloc [alloc.c:390]
> regex_compile [regex.c:3099]
> re_compile_pattern [regex.c:5953]
> compile_pattern_1 [search.c:143]
> compile_pattern [search.c:186]
> string_match_1 [search.c:387]
It does look pretty suspect. There is loads of 'passing the pointer
being done'. How rare are systems without REGEX_MAY_ALLOC? I suspect
this case is exercised less. However it migth well be that the
particular rexexp ist just never GCed.
Well, if it is a real memory leak, it's not being caused by GC.
This particular memory block is part of a non-lisp global variable.
However, I can't find any place where this leak could be caused. I'm
wondering if temacs is zero'ing some global memory before it exit()'s
(in which case this would not be a real leak).
If I have time (which I probably don't), I'll try to step through
temacs to see where the leak is occurring.
--
Darryl Okahata
darrylo(a)sr.hp.com
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Hewlett-Packard, or of the
little green men that have been following him all day.