Comment 3 for bug 416990

We know bzr can use a lot of memory, but telling us that won't help us
fix it - we already know.

To fix it we need to know what *that specific process was doing*, so
that we can reproduce, test, analyse and fix.

Getting:
 - the branch being operated on
 - how many packs and indices the branch had, its format
 - what smart server verbs were called

would be great.

The first is essential to have any hope of debugging. the latter is also
extremely important. The middle detail would be gravy.

-Rob

 tags memory
 importance high
 status confirmed
 done