[EMAIL PROTECTED] wrote:
Hello David,
thanks for your help.
Can you show us
otavio$ darcs changes -s
please?
Output here:
http://www.viridian-project.de/darcs/parted/otavio/changes.txt
Or is this an accessible repository.
Find them all here:
http://www.viridian-project.de/darcs/parted/
Also, pull is always more efficient than push, so pulling
might work fine.
Same problem:
1.8.x$ darcs pull ../otavio/
Fail: realloc: resource exhausted (out of memory)
Interestingly enough, when I try to build darcs from source, I also get
an "out of memory" error somewhere. It seems to be GHC that's eating
all the mem...
Maybe your virtual server has set a limit on the data size for a process, that
may be smaller than the total memory size allocated to the virtual machine. You
said earlier that it was using 160M, how did you measure that?
If you run darcs with "+RTS -sstderr" you'll see how much memory the GHC heap
was using (look for the "in use" figure). But the GHC runtime doesn't allocate
memory via realloc(), it uses mmap(), so this is probably memory that darcs
itself is allocating.
Cheers,
Simon
_______________________________________________
parted-devel mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/parted-devel
