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

[Marijn Vriens]

On Thu, Jul 16, 2009 at 4:55 PM, Matt Mackall <mpm at selenic.com> wrote:

> On Thu, 2009-07-16 at 10:04 -0400, Greg Ward wrote:
> > On Thu, Jul 16, 2009 at 8:30 AM, Marijn Vriens<marijnvriens at gmail.com>
> wrote:
> > > 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.
> >
> > 200 MB of small-to-medium files should not be a problem.  Do you have
> > any really large files in there?  That is the usual cause of
> > out-of-memory errors.
> >
> > (See http://mercurial.selenic.com/wiki/HandlingLargeFiles if you're
> > interested in gory technical details.)
>
> There have been some bugs uncovered recently with memory usage for large
> sets of copies. These have been fixed in the -stable branch and should
> be released as 1.3.1 shortly.


I can add to this report that generating diffs between two biggish source
trees (200M) will fail with memory allocation issues in 1.3. The same
command on the same trees succeed with 1.2.1 (resulting in a 142M git
patchfile.. but well :) )



>
>
> --
> http://selenic.com : development and support for Mercurial and Linux
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://selenic.com/pipermail/mercurial/attachments/20090716/49dfa3ff/attachment.htm