[issue1842] "abort: out of memory" when attempting to update large repo on Windows
Benjamin Pollack
bugs at mercurial.selenic.com
Thu Sep 24 22:24:32 UTC 2009
New submission from Benjamin Pollack <benjamin at bitquabit.com>:
We have a large (1.9 GB) repository. The repository cannot be cloned to a
Windows machine, failing with "abort: out of memory", and attempts to update
from nullrev fail with the same. Oddly, if an already-updated repository is
copied directly to the machine, the user may commit, pull, and push as normal-
-provided, of course, that they never go back to revision 0 or delete all of
their files. The problem does not appear on Macintoshes. The problem appears
on Windows with both 1.3.0 and 1.3.1. I have not tested 1.2.1 and lower, but
am happy to do so if that would be helpful.
----------
messages: 10568
nosy: benjamin
priority: bug
status: unread
title: "abort: out of memory" when attempting to update large repo on Windows
____________________________________________________
Mercurial issue tracker <bugs at mercurial.selenic.com>
<http://mercurial.selenic.com/bts/issue1842>
____________________________________________________
More information about the Mercurial-devel
mailing list