Comment 7 for bug 382795

We have verified the following on staging and on my laptop:
 - Without C extensions, 'bzr branch offending-branch /tmp/wibble' skyrockets in memory
 - With C extensions, it reaches about 1.1g -- a lot, but manageable.
 - Regardless of whether C extensions are installed, the puller cronscript rapidly consumes all available memory when pulling offending-branch.

To resolve this, we will:
 - Try upgrading to 1.15 and see if the bug has been magically fixed.
 - Land a branch that uses setrlimit to cap the amount of memory used.

Once this is done, we'll be able to downgrade this bug from critical to high and to re-enable the offending branch. Note that the branch will probably still fail to mirror, since we have not addressed the underlying bug.

To find the underlying bug, we should probably use py_memory_dump to examine how the memory is being consumed. We might also want to pare the puller down into its bare essentials so as to reproduce the problem with minimal code.