Re: [jamboost] more on leaks

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-07-04 10:37:22

Oh, one further note: with this newstr.c change, the leaks due to newstr.c
should disappear from the valgrind output, since we now clean up the blocks
allocated to these strings when bjam exits.

It doesn't change the fact that they /are/ leaked, but the output should be
a little less distracting ;-)

-Dave

----- Original Message -----
From: "David Abrahams" <david.abrahams_at_[hidden]>
To: <jamboost_at_[hidden]>
Sent: Thursday, July 04, 2002 11:34 AM
Subject: [jamboost] more on leaks

> I added a block allocator to newstr.c in order to speed allocations and
> reduce internal fragmentation. It seemed to make about a 10% difference
in
> memory use for my test case.
>
> One other thing I noted was that as build actions execute, bjam seems to
> continue to chew through lots of memory, at least on NT. I'm not sure of
> the cause. I think the filename of the temporary .bat file used by
command
> execution is definitely being leaked, but that should be insignificant,
> even in a run with lots of build actions.
>
> -Dave
>
> +---------------------------------------------------------------+
> David Abrahams
> C++ Booster (http://www.boost.org) O__ ==
> Pythonista (http://www.python.org) c/ /'_ ==
> resume: http://users.rcn.com/abrahams/resume.html (*) \(*) ==
> email: david.abrahams_at_[hidden]
> +---------------------------------------------------------------+
>
>
>
> To unsubscribe from this group, send an email to:
> jamboost-unsubscribe_at_[hidden]
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>