Re: [jamboost] memory leakage?

From: Vladimir Prus (ghost_at_[hidden])
Date: 2002-07-03 10:17:04

David Abrahams wrote:
> From: "Vladimir Prus" <ghost_at_[hidden]>
>
> > 1. We still have memory leaks.... see the attached file. The top memory
>
> leak
>
> > is that all strings are allocated using newstr but never freed.
>
> We're going to have to fix this in the end. When I try to build with all of
> my compilers in libs/python/test, the memory image is 70Meg. :(

What I was trying to say is that "newstr" is probably not the worst problem. 
There may be a lot of memory allocated during the jam run but is freed at the 
end. So, strictly speaking, there's no memory leak -- just inefficient memory 
usage. If this is the case, I suspect a major overhaul would be required to 
fix it.

- Volodya