From: Stefan Kangas <stefan@marxist.se>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Thierry Volpiatto <thievol@posteo.net>, 51763@debbugs.gnu.org
Subject: bug#51763: 27.2; Displaying many images take all memory
Date: Thu, 11 Nov 2021 09:33:39 -0800 [thread overview]
Message-ID: <CADwFkmnR+PvPKSywKnukL78N2Ze+HOJOimR+74FfDH=XNddt4A@mail.gmail.com> (raw)
In-Reply-To: <875ysy6f39.fsf@gnus.org>
Lars Ingebrigtsen <larsi@gnus.org> writes:
> We've previously discussed adding a parameter to image-size to disable
> this caching. Perhaps we should just do that?
I didn't follow those discussions, but that's what I think we should do
as well.
Should we perhaps also add a max cache size in addition to the
`image-cache-eviction-delay'? I find it easy to get memory usage up to
several GiB when viewing large images, and all that happens in less than
five minutes. (That would be a separate feature request though, as this
bug is about the memory usage regression introduced in Image-Dired.)
Relatedly, image-mode could be smarter, and evict images manually from
the cache. Let's say that when flipping through images in a directory,
we only keep the previous N images (where N is, like, 5 or something).
next prev parent reply other threads:[~2021-11-11 17:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 9:00 bug#51763: 27.2; Displaying many images take all memory Thierry Volpiatto
2021-11-11 9:50 ` Stefan Kangas
2021-11-11 11:22 ` Thierry Volpiatto
2021-11-11 17:33 ` Stefan Kangas
2021-11-11 18:11 ` Thierry Volpiatto
2021-11-11 12:39 ` Lars Ingebrigtsen
2021-11-11 17:33 ` Stefan Kangas [this message]
2021-11-12 3:30 ` Lars Ingebrigtsen
2021-11-12 4:03 ` Stefan Kangas
2021-11-12 6:24 ` Lars Ingebrigtsen
2021-11-13 7:32 ` Thierry Volpiatto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADwFkmnR+PvPKSywKnukL78N2Ze+HOJOimR+74FfDH=XNddt4A@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=51763@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=thievol@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.