hg pull runs out of memory

[Steve Borho]

On Wed, Apr 25, 2012 at 4:24 AM, Hertroys A. <
alban.hertroys at apollovredestein.com> wrote:

>      Hi,****
>
> ** **
>
> I’m running into a “slight” problem again trying to synchronise my local
> repository with our central one: hg pull  runs out of memory on one of
> our change-sets…****
>
> ** **
>
> I managed to isolate the change-set (1110) and it contains a couple of
> large binary files that were added accidentally. They were removed again a
> couple of change-sets later (1112). My clone is updated to 1109 now, but I
> can’t get it past there!****
>
> ** **
>
> The current situation (locally):****
>
> ** **
>
> C:\ibi\apps>hg --version****
>
> Mercurial Distributed SCM (version 2.1.2)****
>
> ** **
>
> C:\ibi\apps>hg tip****
>
> changeset:   1109:982a777c40ae****
>
> tag:         tip****
>
> …****
>
> ** **
>
> This is what happens:****
>
> ** **
>
> C:\ibi\apps>hg pull -v -u -r 1110****
>
> pulling from Z:\ibi\apps****
>
> searching for changes****
>
> all local heads known remotely****
>
> 1 changesets found****
>
> adding changesets****
>
> adding manifests****
>
> adding file changes****
>
> transaction abort!****
>
> rollback completed****
>
> abort: out of memory****
>
> ** **
>
> The remote tip is at 1119, so 10 change-sets to pull still…****
>
> ** **
>
> Hg is churning up to just over 900MB of memory when it aborts. The binary
> files (which are in fact unwanted in the repo) are a couple of 100 MB’s in
> size each.****
>
> ** **
>
> How do I proceed?
>

A 64bit version of Windows will resolve these memory errors altogether.  As
a workaround you can try:

hg pull -v -r 1109
hg pull -v -r 1110
hg pull -u

-- 
Steve Borho
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20120425/73a9b4c5/attachment-0002.html>