On 3/13/06, Aaron Kaplan <[EMAIL PROTECTED]> wrote: > I've gotten no help for this problem so far. Now it's not just check > but also record that is using up all of the available virtual memory, > bringing my system to its knees every time I try it. I've had to back > off to darcs 1.0.4, which doesn't have the problem.
I'm not sure if it is related or not...but I found that some versions of darcs are very poor at reading in recorded patch data. http://codersbase.com/index.php/Darcs_performance Since you are talking about recording you could be having a similar problem. Do you have any large files in the directory? Even ones which are not under the controll of darcs can be a problem for some operations such as whatsnew. Thanks, Jason > > -Aaron > > > On Thu, 02 Mar 2006 17:44:20 +0100, "Aaron Kaplan" > <[EMAIL PROTECTED]> said: > > I have a repo where darcs check with darcs 1.0.6 or 1.0.5 consumes 2GB > > of virtual memory and eventually dies without having completed the > > check. Darcs 1.0.4 finishes the check consuming only about 80MB, and > > reports that the repo is consistent. > > > > I don't know if this is related, but there's also a patch in this repo > > that I tried to unrecord, and I got the error message "darcs: bug in > > get_extra commuting patch:". The bugs related to this error message > > that I found on the web weren't relevant: I've never used darcs 1.0.0, > > and there are no two patches in this repo with the same timestamp. > > > > Any debugging hints? Unfortunately, I can't make the repo available. > > > > Thanks > > -Aaron > > _______________________________________________ > darcs-users mailing list > [email protected] > http://www.abridgegame.org/mailman/listinfo/darcs-users > > _______________________________________________ darcs-users mailing list [email protected] http://www.abridgegame.org/mailman/listinfo/darcs-users
