Comment 3 for bug 293679

Hmm, I can't reproduce your problem. I have found another problem, but it doesn't seem to be this severe, and it is unchanged between 1.8 and 1.9rc1.

Unfortunately that traceback isn't very helpful either, because it's showing an error during the abort, rather than where it was when it was aborted :(

Can you repeat again with -Dhpss, and attach the .bzr.log? Feel free to interrupt it before it consumes all your memory! The -Dhpss output in ~/.bzr.log should give a fairly good indication of where it got up to when it reached that point.