Crash in bzr-svn

[Paul Moore]

On 28/02/2008, Alexander Belchenko <bialix at ukr.net> wrote:
> My error is similar as in bug https://bugs.launchpad.net/bzr-svn/+bug/190832.

Yes, that looks the same as I see.

>
>  But I don't understand comment from Jelmer
> (https://bugs.launchpad.net/bzr-svn/+bug/190832/comments/2):
>
>  "This is a known issue in the http(s) support in the 0.4 branch at the moment. It should
>  work fine in any releases."
>
>  known issue ... should work fine?
>
>  I know my English is bad. But this comment leads me to complete misunderstanding
> of situation.

No, your English isn't that bad. It doesn't make any sense to me either.

I can confirm that I just had another failure which occurred just as
memory usage hit 100%. It looks almost certain that this is an error
caused by running out of memory. What I don't understand is why bzr
keeps using more and more memory - it seems to me that something is
failing to release memory as it should.

Paul.

PS I'm trying your suggestion of bzr pull in stages at the moment. It
looks like it's working OK. Oddly, though, I got a message "Conflict
adding file Demo/sgi/video/Vinfo.py.  Moved existing file to
Demo/sgi/video/vinfo.py.moved.
Conflict adding file Demo/sgi/video/Vtime.py.  Moved existing file to
Demo/sgi/video/vtime.py.moved." I'm not quite sure how I get a
conflict pulling from a (presumably consistent) svn repository...