Comment 16 for bug 602614

Its all remote... I finally got past the issue by using "push" to send the tree into the server instead of "pull" or "update". I have 3 remote servers, 2 servers that produce a bzr: out of memory and one server that will not (each has 2Gb), but the server that works is our dev server, running a much lighter load. I guess I could try to get more memory, but this really shouldn't be happening. If it gets the point where we have to rebuild the tree from scratch I might jump ship over to svn if no one has fixed this yet. Kinda frustrating when your trying to deploy new software.... Thanks treaves...