"abort: out of memory" when running "hg up".

[Marijn Vriens]

Hi all,

Got the following session from mercurial.

My repository's first few commits are importing an existing  and
restructuring. It is a largish (200M) code base. Jumping from rev 0 to 1 is
a big changeset indeed.

The machine is a Macbook pro with 2gigs of mem, that was not particularly
memory starved when this happened.

$ hg clone sos-work sos-back
updating working directory
12418 files updated, 0 files merged, 0 files removed, 0 files unresolved
$ cd sos-back/
$ hg up -r0
19 files updated, 0 files merged, 7180 files removed, 0 files unresolved
$ hg up -r1
Python(6230) malloc: *** mmap(size=1052672) failed (error code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
Python(6230) malloc: *** mmap(size=421888) failed (error code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
abort: out of memory
$  hg id
5fb255525a5f 0 default
$ hg up -r1
/Users/mvriens/lib/python/mercurial/lock.py:71: DeprecationWarning: use
lock.release instead of del lock
  locker = self.testlock()
Python(6232) malloc: *** mmap(size=1052672) failed (error code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
Python(6232) malloc: *** mmap(size=421888) failed (error code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
abort: out of memory
$ hg --version
Mercurial Distributed SCM (version 1.3)

Copyright (C) 2005-2009 Matt Mackall <mpm at selenic.com> and others
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.



Regards,
       Marijn Vriens.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://selenic.com/pipermail/mercurial/attachments/20090716/14853c4a/attachment.htm