Package: darcs
Version: 2.4.3-1
Severity: normal

Hi,

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'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.

Also subjectively, darcs has got a bit slower as of a few
days or weeks. This might be related.

Ciao.                                                Vincent.

Vincent,

Vincent Zweije wrote:

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.

I think this is an unrelated new feature.

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.

In view of the above, I gree.

Thanks.                                              Vincent.