|
From: Jeremy F. <je...@go...> - 2005-02-26 00:11:53
|
Julian Seward wrote:
> I hesitate to run the leak checker by default at exit. It can
> cause a huge amount of disk activity because it inspects bits of
> address space that had been swapped out during long runs of
> leaky programs, and which then gets forced back in as the checker
> traverses it all.
>
> But perhaps we should. In an underhand way it creates the
> expectation amongst programmers that their programs should have
> no detectable leaks, and that leaks will be tested for routinely
> -- every time V is run.
Well, since it's mark-sweep now, a basic leak check only traverses the
live heap. We could report the total number of leaked blocks/memory
pretty quickly. Its only doing a decent job of reporting specific leaks
which requires walking the leaked part of the heap.
Also, the checker touches a lot less memory than it used to; it doesn't
bother scanning read-only memory, for example (since it can never
contain pointers to the heap).
J
|