On Mon, Jun 07, 2010 at 06:26:38PM +1000, [email protected] wrote: > Vincent Zweije wrote: > > Recently, darcs whatsnew --look-for-adds --boring eats up all memory > > (on this 4 Gb system) on a fairly sizable repository (and still > > produces no output). > > I think this might be http://bugs.darcs.net/issue1746. Do you agree? > If so, I'll link this Debian ticket to that Darcs one.
Yes. The boring new files are in fact many object and archive files, totaling several gigabytes. Reading those into memory is not going to work. As added information to that ticket, I don't think the combined size of the boring files should be considered improbably large. We compile for up to 8 configurations at the same time (32/64 bit, position dependent and independent, and with and without optimization), and with debug symbols and all, gigabytes is not hard to reach. In short, darcs should not assume the boring files are going to fit into memory. > > I'm thinking the gzcrc check feature might be responsible for this, > > because subjectively, the gzcrc warnings started to appear at the > > same time. I'm assuming some darcs update introduced this. > > I think this is an unrelated new feature. In view of the above, I gree. Thanks. Vincent. -- WCC - Smart Search & Match NL +31 30 7503222 [email protected] www.wcc-group.com
signature.asc
Description: Digital signature
