Comment 1 for bug 186014

Hi,

Thanks for your bug report.

I am interested in what is causing the problem that you are
seeing. From the traceback I would guess that it is using a
lot of memory to read the dirstate (the on disk representation
of the state of the working tree).

Is this an open source project? If so can we have a copy of
the code to try and reproduce this. If not could we just have
the dirstate? It lists the filenames, but should not give any
more information than that. Failing that just the size
of the dirstate file would a start (ls -l .bzr/checkout/dirstate)

Is there any improvement if you branch the project to a different
location (on the same machine) and then make the changes?

Thanks,

James