GNU bug report logs - #33275
27.0.50; Image cache pruning

Previous Next

Package: emacs;

Reported by: Lars Ingebrigtsen <larsi <at> gnus.org>

Date: Mon, 5 Nov 2018 14:09:02 UTC

Severity: normal

Tags: fixed

Found in version 27.0.50

Fixed in version 27.1

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 33275 <at> debbugs.gnu.org
Subject: bug#33275: 27.0.50; Image cache pruning
Date: Mon, 05 Nov 2018 17:35:51 +0100
Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: Lars Ingebrigtsen <larsi <at> gnus.org>
>> Cc: 33275 <at> debbugs.gnu.org
>> Date: Mon, 05 Nov 2018 17:18:47 +0100
>> 
>> If you visit a, say, 16GB file, then, indeed, it's expected that Emacs
>> grows to 16GB (or more).  But if you're just calling `image-size' on a
>> bunch of files (each of which is a lot smaller than that), it's rather
>> unexpected that that's going to blow up Emacs.
>
> What was the sum of sizes of all the files you used to reproduce the
> problem?

I think it's sufficient to run Emacs over 2GB worth of .png files to
make Emacs grow to 16GB (which will kill it on this laptop).

But it'll vary on how well-compressed the .png files are, I guess,
because I think Emacs caches the, er, pixmaps and not the files?  I
don't remember.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no




This bug report was last modified 5 years and 239 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.