Comment 7 for bug 690021

I'm unassigning myself because I do not intend to do any more on this right now, but I am happy to help with this.

My landing should make this fail cleanly/safely without hitting the kernel oomkiller. We may even get a traceback/oops out of it, which would make it easier to understand just what is going wrong. If we don't get that, it would at least be nice to identify a particular branch that blows up.

lp is currently running 2.2.3dev, and there have been a lot of memory usage improvements since then. It is possible this problem will be fixed by upgrading to bzr2.4b for which other work is underway.