Comment 34 for bug 456077

And 30 minutes after killing the above "bzr branch" job on my local machine, the bzr process on the remote machine is still running at 100% CPU. I suspect that this is a bug. There should be reasonably periodic detection, on the remote side, that the local side process has gone away. Otherwise the warning, even if it is printed, loses interest (it warns you, you control-C your bzr command, but it still hogs the remote machine for a long time).
Some piece of information, maybe useless: on the local machine, when I killed bzr after it had exchanged 300MB on the network and ran for 4 hours, my branch was only 8KB.