Re: cvs2hg memory use

On Tue, Aug 4, 2009 at 4:31 PM, Michael Haggerty<[email protected]> wrote:
> Actually, I expect that cvs2hg only generates garbage in OutputPass, so
> you might consider enabling garbage collection only in that pass and
> have the best of both worlds.

Already covered: I call gc.enable() in HgOutputOption.setup() so that
cvs2hg does not leak like a sieve running under Mercurial 1.3, and
then I call gc.collect() from cleanup() to dodge the
check_for_garbage() bullet.  Seems to work.  I'm still curious as heck
why it leaks under 1.3, but have bigger fish to fry at the moment.
(Like, actually getting a working conversion from CVS, which is
tantalizingly close but painfully slow because of the stupid way I
implemented tag fixup commits.  Correctness first, then
performance...)

Greg