bzr-svn 0.4.9 - still with memory leaks?

[Paul Moore]

On 27/03/2008, Matt Nordhoff <mnordhoff at mattnordhoff.com> wrote:
>  I myself converted Python too. It went well, but since I'm still on a
>  leaky version of Subversion, I did it 500 or 1000 revisions at a time so
>  it wouldn't use all my RAM.

Interesting. It sounds like the lessons from all this are:

1. Make the initial cloning by pulling in batches.
2. If the repository has case clashes anywhere in history, you need to
use Unix for the initial clone.

Fixing the leaks in bzr-svn would solve the first (at the moment,
either the Windows binaries don't include the python-svn leak fixes,
contrary to what I understand, *or* there are other leaks which
haven't been addressed yet, *or* memory use is expected to grow as the
number of revisions being pulled, which could do with being
documented).

A robust solution to case (in)sensitivity issues in Bazaar would
resolve the second one [1]. The second is the worst issue, as there
isn't a workaround.

Paul.

[1] By "robust", I mean something that ensures that pulling in batches
through a case issue results in an identical repository to the one
you'd get on a case sensitive system - this is a lot harder than just
resolving clashes in the working directory files.