Comment 4 for bug 522296

Quick experiments with different versions, on the same 1.14 repo as above:

bzr.dev, 1.18.1:
They first do a check of each branch (fast) then go into
 checking commit contents:inventories 0/2
After 11 mins RAM starts growing from 6% to 50% (i.e. 6GB...)
I do control-C and see that bzr is in:
> bzrlib/osutils.py(656)sha_strings()
-> map(s.update, strings)

1.15.1, 1.17:
Seem to do things differently:
No working tree found at specified location.
Checking repository at 'file:///home/mysql_src/from_bk_internal/guilhem/'.
[###############/ ] checking revision graph:Checking cached revision graph 53000/87653
then goes into a 24-hour-long
[\ ] checking revision 3/87653
where RAM stays <6%.

So possibly this RAM consumption is a bug introduced between 1.17 and 1.18.1. Now I'm letting this for you to look at :-)